Cancel a specific queued action by ID, or cancel all pending actions. Items currently processing will run to completion.
AI agents call queue_cancel to permanently remove resources in Reddirect — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Cancelling queued actions permanently removes them from the processing pipeline. Since 'items currently processing will run to completion' but cancelled items will never execute, this is an irreversible deletion of pending operations. While not deleting user content, it irreversibly destroys scheduled/queued work, placing it in the Destructive category.
From the tool's definition 'Cancel a specific queued action by ID, or cancel all pending actions' — cancelling queued actions is irreversible; once cancelled, those pending operations are permanently removed from the queue and cannot be recovered.
Attacks that exploit this kind of access
Cancel a specific queued action by ID, or cancel all pending actions. Items currently processing will run to completion. It is categorised as a Destructive tool in the Reddirect MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Reddirect MCP server in PolicyLayer and add a rule for queue_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 Reddirect. Nothing to install.
queue_cancel 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 queue_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 queue_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.
queue_cancel is provided by the Reddirect MCP server (jeebus87/reddirect). 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 →