AI agents invoke scout_handoff_cancel to trigger actions in Scout. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
This tool triggers an external operation in the browser — cancelling a pending handoff and removing UI elements. It modifies browser state and cancels an in-progress operation, making it an Execute-category action. The blast radius is medium because cancelling a handoff could interrupt workflows, but it is not inherently destructive or financial.
From the tool's definition Cancel a pending handoff and remove the banner from the browser
Attacks that exploit this kind of access
Cancel a pending handoff and remove the banner from the browser. It is categorised as a Execute tool in the Scout MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Scout MCP server in PolicyLayer and add a rule for scout_handoff_cancel: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches Scout. Nothing to install.
scout_handoff_cancel is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the scout_handoff_cancel rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.
Set action: deny in the PolicyLayer policy for scout_handoff_cancel. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.
scout_handoff_cancel is provided by the Scout MCP server (lautrek/scout). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →