Critical Risk →

delete_queue

Delete a queue.

Part of the Queue Pilot server.

delete_queue can permanently delete data in Queue Pilot, with no limits today. PolicyLayer puts allow, deny, and rate-limit rules on every call. Live in minutes.

SECURE QUEUE PILOT →

Free to start. No card required.

AI agents may call delete_queue to permanently remove or destroy resources in Queue Pilot. Without a policy, an autonomous agent could delete critical data in a loop with no way to undo the damage. PolicyLayer blocks destructive tools by default and requires explicit human approval before enabling them.

Without a policy, an AI agent could call delete_queue in a loop, permanently destroying resources in Queue Pilot. There is no undo for destructive operations. PolicyLayer blocks this tool by default and only allows it when a human explicitly approves the action.

Destructive tools permanently remove data. Block by default. Only enable with explicit approval workflows.

policy.json
{
  "version": "1",
  "default": "deny",
  "hide": [
    "delete_queue"
  ]
}

See the full Queue Pilot policy for all 25 tools.

Get this rule live on your own Queue Pilot server in minutes. PolicyLayer enforces it on every call, before it runs.

ENFORCE ON MY QUEUE PILOT →

View all 25 tools →

These attack patterns abuse exactly the kind of access delete_queue gives an agent. Each links to the full case and the policy that stops it:

Browse the full MCP Attack Database →

Every attack above starts with a tool call. PolicyLayer checks each one against your policy first, so delete_queue only ever does what you allow.

SECURE QUEUE PILOT →

Other destructive tools across the catalogue. The same approach applies to each: deny by default, or require human approval.

What does the delete_queue tool do? +

Delete a queue.. It is categorised as a Destructive tool in the Queue Pilot MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on delete_queue? +

Register the Queue Pilot MCP server in PolicyLayer and add a rule for delete_queue: 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 Queue Pilot. Nothing to install.

What risk level is delete_queue? +

delete_queue is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit delete_queue? +

Yes. Add a rate_limit block to the delete_queue 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.

How do I block delete_queue completely? +

Set action: deny in the PolicyLayer policy for delete_queue. 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.

What MCP server provides delete_queue? +

delete_queue is provided by the Queue Pilot MCP server (queue-pilot). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Queue Pilot tool call.

Deterministic rules across all 25 Queue Pilot tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

4,600+ MCP servers and 31,000+ tools scanned and risk-classified.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.