Prompt-injection filtering isn't a security boundary — enforce at the action layer

vasuman · x · 2026-11-19

Prompt-injection filtering alone can't be an agent security boundary: OWASP maps nine dimensions and a filter tuned for one misses the others, so enforcement must sit at the action layer. Concrete layered design: per agent-to-tool integration, combine input filtering, a logged runtime check per action (allow/ask/block against a declared policy), and a damage-limiting sandbox. Example for a DB-accessing agent: reads allowed, writes need human approval, schema changes and exports blocked, all in an isolated sandbox with scoped credentials.

Original post →

More from coding & agent

coding & agent channel →