Engagement session
The interaction with the decoy is captured as an engagement session so the behaviour can be reviewed rather than lost.
MCP firewall capability
Active Agentic Deception
Decoys that live where the agent looks. IntentGate plants decoy tools and injection canaries in the agent’s MCP tool surface; when an agent—or an injected instruction—touches one, it trips, is captured as an engagement session, and mirrored to the console for monitoring, with believability and coverage tracking.
A trip in the tool surface, captured and mirrored
The decoys sit alongside the real tools the agent can see. A touch that a legitimate task would never make becomes a signal.
Agent or injected instructionA hijacked agent, or a poisoned instruction steering it, reaches for a tool it was never asked to use.
Decoy tools & canariesPlanted in the MCP tool surface. Believable enough to be reached for, inert enough to do nothing real.
Trip capturedThe touch is recorded as an engagement session rather than forwarded anywhere.
From a trip to threat intel
What the deception layer produces is evidence: who reached, for what, in which session, mirrored to the console for monitoring.
Mirrored to Monitor
The trip is mirrored to the console Monitor view so an operator sees a hijacked agent in the act.
Believability & coverage
The layer tracks believability and coverage of the planted decoys, so the deception surface can be tuned over time.
What this is, and is not
Deception is a precise word here. This is deception in the agent’s tool surface, not a honeypot on the host or the network.
Deception in the MCP tool surface
The decoys are tools and canaries in the agent’s own context. This is not a host honeypot, an endpoint sensor, or a network deception grid.
It catches a hijacked agent, not a network intruder
The signal is an agent reaching for something it should not. It complements, but does not replace, endpoint and network detection.
Depth is honest about the roadmap
Planting, tripping, capture, and console mirroring are the shape of the control. Richer automated response and correlation deepen over time and are described as roadmap where they are.
Empty until something trips
With no trips, the Monitor view is honestly empty, no fabricated trip counts, no invented coverage score, no sample incidents.
Related capabilities
Each control sits on the same MCP firewall decision path. Explore the neighbouring runtime capabilities.