Agent-to-Agent Delegation Is an Authority Boundary
Why multi-agent delegation needs scoped identities, independent authorization, approval boundaries, revocation, and a reconstructable evidence chain.
Read Field Note
Resources
Start with the agent risk boundary, then move into threat patterns, enterprise lessons, field notes, and focused answers for production-bound AI systems.

The collection is organized around practical enterprise questions: what an agent can do, where it can fail, how controls are validated, and what evidence remains reviewable.
A practical guide to authority, tools, identity, context, controls, and runtime evidence.
Explore 02Threat families for agentic workflows, connected to control questions and business impact.
Explore 03Focused pages for MCP server security, tool controls, prompt injection, testing, and data exposure.
Explore 04Retrieval security guidance for testing, prompt injection, data leakage, citations, memory, and logs.
Explore 05Short answers to common enterprise questions about AI agent security and production readiness.
Explore 06Practical thinking on autonomous AI security, governance, red teaming, and secure engineering.
Explore 07Anonymous patterns from AI risk assessment, red teaming, governance, and assurance work.
ExploreFeatured Field Note
Practical field notes and anonymous patterns for teams making autonomous AI safer to operate.
Why multi-agent delegation needs scoped identities, independent authorization, approval boundaries, revocation, and a reconstructable evidence chain.
Read Field Note
Latest Field Notes

Why multi-agent delegation needs scoped identities, independent authorization, approval boundaries, revocation, and a reconstructable evidence chain.
By Hakan Şen · Sep 18, 2026
A practical approach to bounded autonomy: match human approval to consequences, reversibility, authority, evidence, and tested containment.
By Krishnaveni Gorijavolu · Sep 18, 2026
MCP security should treat every connected server as an extension of the agent's authority, with narrow permissions, clear identity, independent controls, and reviewable evidence.
By Hakan Şen · Sep 7, 2026Enterprise Case Studies
No customer names, logos, exact metrics, or confidential implementation details.
An anonymous pattern for reviewing agent workflows before they interact with sensitive enterprise systems.
Explore Case Study