Zero-Trust Capability Delegation for MCP Agents: How I Built AgentBond
AgentBond makes agent delegation trust by contract, not trust by accident. The Problem Nobody Is Talking About Every on-call engineer who has handed off an investigation to an AI agent and watched ...

Source: DEV Community
AgentBond makes agent delegation trust by contract, not trust by accident. The Problem Nobody Is Talking About Every on-call engineer who has handed off an investigation to an AI agent and watched it call something it was never supposed to call knows this problem. The MCP spec defines how agents call tools. It does not define what a worker agent is allowed to call. When an orchestrator delegates work to a worker agent today, the worker inherits everything. There is no scope. There is no expiry. There is no audit trail. If the worker calls a tool outside its mandate, nothing stops it. If it tries to re-delegate to another agent, nothing stops that either. This is the confused deputy problem. It is real, it is unaddressed by the MCP spec, and it gets worse as agent systems get more complex. AgentBond fixes it. The Distinction That Matters LLM agents decide what they want to do. AgentBond decides what they are actually allowed to do. These are different layers: Layer Examples What it does