Stop a schedule from firing further ticks. In-flight ticks are
AI agents call cancel_schedule 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.
Cancelling a schedule is an irreversible action: once stopped, the schedule no longer fires future ticks and there is no indication of an undo/restore mechanism. This makes it Destructive rather than Write. Severity is medium because while it disrupts automated scheduling, it does not delete data or code directly — the blast radius is limited to missed scheduled executions.
From the tool's definition 'Stop a schedule from firing further ticks' — permanently halts a schedule, which cannot be undone once cancelled
Attacks that exploit this kind of access
Stop a schedule from firing further ticks. In-flight ticks are. 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_schedule: 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_schedule 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_schedule 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_schedule. 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_schedule 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 →