Clear handoffs. If key is provided, clears only that handoff. Otherwise clears all.
AI agents call handoff_clear to permanently remove resources in Conversation Handoff MCP — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
An AI agent that decides to call handoff_clear doesn't hesitate, doesn't double-check, and doesn't stop at one. Whatever it removes from Conversation Handoff MCP is gone — there is no undo for destructive operations.
Attacks that exploit this kind of access
Clear handoffs. If key is provided, clears only that handoff. Otherwise clears all. It is categorised as a Destructive tool in the Conversation Handoff MCP MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Conversation Handoff MCP server in PolicyLayer and add a rule for handoff_clear: 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 Conversation Handoff MCP. Nothing to install.
handoff_clear is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the handoff_clear 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 handoff_clear. 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.
handoff_clear is provided by the Conversation Handoff MCP server (trust-delta/conversation-handoff-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.