Unverified50% confidenceSolutionExact time
Common defenses against prompt injection include input filtering, tool whitelisting, least privilege, and separating untrusted content from instructions during processing.
1
Sources
50%
Confidence
Long-term
Relevance
10/29/2026
First Seen
Sources
Related Entities
Related Claims
UnverifiedInput filtering alone can hardly provide exhaustive defense against indirect prompt injection, because plausible-looking instructions can be naturally embedded in legitimate documents; a more reliable approach is to treat read content as untrusted and limit, at the tool call boundary, what follow-up actions it can trigger.78% similarUnverifiedBecause LLMs cannot strictly distinguish 'instructions' from 'data' the way traditional programs do, prompt injection is difficult to eradicate with a single filter and usually requires a combination of defense-in-depth measures such as bidirectional input-output detection, least privilege, and tool-call whitelists.73% similarUnverifiedGuardrails based on keyword blocking can be evaded by users simply by rephrasing their expressions.72% similarUnverifiedJailbreak prompts are a class of specially designed input text whose goal is to induce large language models to bypass safety alignment mechanisms and output responses that should have been restricted.71% similarUnverifiedMinimal mode strips away most formatting instructions and safety guardrail prompts, exposing the model more directly to user input.70% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/1112597API
curl https://kongchang.com/api/v1/knowledge/claims/1112597MCP
get_claim(id=1112597)