cancel_dispatch
AI agents call cancel_dispatch to permanently remove resources in Claude Bridge — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
The description is empty, so classification relies on the tool name alone. 'cancel_dispatch' most likely terminates/cancels a dispatched job or operation irreversibly. Given sibling tools like 'cancel_schedule', 'dispatch', and 'dispatch_async', this tool likely cancels an active dispatch — an action that cannot be undone. Confidence is lowered due to lack of description.
From the tool's definition Tool name 'cancel_dispatch' and sibling tools 'dispatch', 'dispatch_async', 'get_dispatch' suggest this cancels an in-flight or scheduled dispatch operation. Cancellation is typically irreversible.
Attacks that exploit this kind of access
cancel_dispatch. It is categorised as a Destructive tool in the Claude Bridge MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Claude Bridge MCP server in PolicyLayer and add a rule for cancel_dispatch: 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 Claude Bridge. Nothing to install.
cancel_dispatch 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 cancel_dispatch 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 cancel_dispatch. 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.
cancel_dispatch is provided by the Claude Bridge MCP server (josiahsiegel/claude-bridge). 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 →