Security & permissions
Scoping what agents can reach, and the attack surface that arrives with tool access.
1 answer · 5 articles · 2 definitions
Definitions in this subject
AI agent permissions: how to scope access down
Scope access per task, not per agent. Give each agent a narrow, short-lived credential for the job in front of it, keep irreversible writes behind an approval or a reversible path, and log what it actually reached rather than what it was allowed to reach. Standing broad grants are the failure mode, and 90 percent of deployed agents carry them.
ArticleMCP authorization decides what context agents see
MCP authorization became a context control plane in 2026. RFC 8707 token scoping decides which sources an agent can ever pull into its own context window.
ArticleWhy 14 MCP CVEs trace back to one design choice
OX Security's April 2026 advisory traces 14 MCP CVEs and 200,000 exposed servers to a single design choice: STDIO as the default local transport.
ArticleAI agents have too much access
88% of organizations report AI agent security incidents. The root cause is a context engineering failure: agents get all-or-nothing access, not scoped context.
ArticleTool poisoning: how MCP tool descriptions hijack agents
Tool poisoning hides instructions inside MCP tool descriptions the agent reads as trusted context. The MCPTox benchmark recorded a 72.8% attack success rate.
ArticleContext Poisoning: When Bad Data Becomes AI Ground Truth
Context poisoning plants false data into an AI agent's memory or RAG index. The model treats it as truth. It's a context engineering problem, not a model bug.
Give your agents one place to read and write.
Put in your docs, data and notes, then connect Claude, Codex or anything else with one link.
Create a container