remove_job

Remove a job from the 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/remove-job.md

WHAT IT DOES

What remove_job does on BullMQ MCP Server

AI agents call remove_job 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 remove_job is rated Critical

Removing a job from a BullMQ queue is an irreversible operation that deletes job data and prevents its execution. This fits the Destructive category as it permanently removes data from the system. The severity is high because an AI agent could inadvertently delete critical jobs from production queues, disrupting business workflows.

From the tool's definition Tool name 'remove_job' explicitly removes a job from the queue. The verb 'remove' combined with the job queue context indicates irreversible deletion of queue data.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs remove_job 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 remove_job, this is the rule to start with:

remove_job Hidden

remove_job 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": [
    "remove_job"
  ]
}

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 remove_job call is checked against it from then on.

FAQ

Questions about remove_job

What does the remove_job tool do? +

Remove a job from the 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 remove_job? +

Register the BullMQ MCP Server MCP server in PolicyLayer and add a rule for remove_job: 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 remove_job? +

remove_job 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 remove_job? +

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

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

remove_job 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

remove_video on Mcptube Vision →delete_cron_job on cPanel MCP Server →remove_concept on MegaMemory →task_assignees_remove on Vikunja → All critical-risk MCP tools → The MCP Attack Database →

Guides

Govern database agents →Blast radius →Tool call approval →