clean_queue

Clean jobs from queue

SERVERBullMQ MCP Server SOURCEadamhancock/bullmq-mcp

Critical RISK CLASS

Category Destructive

Parameters 00 required

Recommended Hiddensee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/adamhancock-bullmq-mcp/clean-queue.md

WHAT IT DOES

What clean_queue does on BullMQ MCP Server

AI agents call clean_queue to permanently remove resources in BullMQ MCP Server, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

RISK

Why clean_queue is rated Critical

Cleaning jobs from a queue permanently removes them, which cannot be undone. This matches the Destructive category. Severity is high because an AI agent misusing this tool could wipe out large numbers of jobs across queues, disrupting workloads irreversibly.

From the tool's definition 'Clean jobs from queue' — removing jobs from a queue is an irreversible deletion of pending/completed/failed job records

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs clean_queue safely

PolicyLayer is an MCP gateway: it sits between your AI agents and BullMQ MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For clean_queue, this is the rule to start with:

clean_queue Hidden

clean_queue is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "clean_queue"
  ]
}

RESTRICT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect BullMQ MCP Server, apply this rule, and every clean_queue call is checked against it from then on.

FAQ

Questions about clean_queue

What does the clean_queue tool do? +

Clean jobs from queue. It is categorised as a Destructive tool in the BullMQ MCP Server 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 clean_queue? +

Register the BullMQ MCP Server MCP server in PolicyLayer and add a rule for clean_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 BullMQ MCP Server. Nothing to install.

What risk level is clean_queue? +

clean_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 clean_queue? +

Yes. Add a rate_limit block to the clean_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 clean_queue completely? +

Set action: deny in the PolicyLayer policy for clean_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 clean_queue? +

clean_queue is provided by the BullMQ MCP Server MCP server (adamhancock/bullmq-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on BullMQ MCP Server, and thousands of servers like it.

This server

All 20 BullMQ MCP Server tools → Critical-risk tools on this server →

Across the catalogue

All critical-risk MCP tools → The MCP Attack Database →

Guides

Govern database agents →Blast radius →Tool call approval →