# remove_job

Remove a job from the queue

Agent View of the PolicyLayer registry record for `remove_job`. HTML page: https://policylayer.com/tools/adamhancock-bullmq-mcp/remove-job

## Facts

- Tool: `remove_job`
- Server: BullMQ MCP Server (`adamhancock/bullmq-mcp`) — https://policylayer.com/tools/adamhancock-bullmq-mcp.md
- Homepage: https://github.com/adamhancock/bullmq-mcp
- Risk category: Destructive (Critical risk)
- Registry record: grade F, identity unverified
- Server rate-limited: no
- Parameters: 0
- Recommended policy verdict: Hidden

## Example call (MCP tools/call, JSON-RPC 2.0)

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "remove_job",
    "arguments": {}
  }
}
```

## 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 own 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."

## Use case

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.

## Recommended policy (PolicyLayer)

Verdict: **Hidden**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches BullMQ MCP Server:

```json
{
  "version": "1",
  "default": "deny",
  "hide": [
    "remove_job"
  ]
}
```

## Other tools on BullMQ MCP Server (19)

- `clean_queue` — Destructive — https://policylayer.com/tools/adamhancock-bullmq-mcp/clean-queue.md
- `drain_queue` — Destructive — https://policylayer.com/tools/adamhancock-bullmq-mcp/drain-queue.md
- `pause_queue` — Execute — https://policylayer.com/tools/adamhancock-bullmq-mcp/pause-queue.md
- `resume_queue` — Execute — https://policylayer.com/tools/adamhancock-bullmq-mcp/resume-queue.md
- `retry_job` — Execute — https://policylayer.com/tools/adamhancock-bullmq-mcp/retry-job.md
- `switch_connection` — Other — https://policylayer.com/tools/adamhancock-bullmq-mcp/switch-connection.md
- `get_job` — Read — https://policylayer.com/tools/adamhancock-bullmq-mcp/get-job.md
- `get_job_logs` — Read — https://policylayer.com/tools/adamhancock-bullmq-mcp/get-job-logs.md
- `get_jobs` — Read — https://policylayer.com/tools/adamhancock-bullmq-mcp/get-jobs.md
- `list_connections` — Read — https://policylayer.com/tools/adamhancock-bullmq-mcp/list-connections.md
- `list_queues` — Read — https://policylayer.com/tools/adamhancock-bullmq-mcp/list-queues.md
- `query_dead_letter_queue` — Read — https://policylayer.com/tools/adamhancock-bullmq-mcp/query-dead-letter-queue.md
- `stats` — Read — https://policylayer.com/tools/adamhancock-bullmq-mcp/stats.md
- `add_job` — Write — https://policylayer.com/tools/adamhancock-bullmq-mcp/add-job.md
- `add_job_log` — Write — https://policylayer.com/tools/adamhancock-bullmq-mcp/add-job-log.md
- `connect` — Write — https://policylayer.com/tools/adamhancock-bullmq-mcp/connect.md
- `disconnect` — Write — https://policylayer.com/tools/adamhancock-bullmq-mcp/disconnect.md
- `move_failed_jobs_to_dlq` — Write — https://policylayer.com/tools/adamhancock-bullmq-mcp/move-failed-jobs-to-dlq.md
- `promote_job` — Write — https://policylayer.com/tools/adamhancock-bullmq-mcp/promote-job.md

## For agents

This record is a snapshot. Live verdicts and the full registry:

- Check every server in your MCP config at once: `npx -y policylayer stack`
- Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md)
- Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events`

---

Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=adamhancock-bullmq-mcp · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/adamhancock-bullmq-mcp