# retry_job

Retry a failed job

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

## Facts

- Tool: `retry_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: Execute (High risk)
- Registry record: grade F, identity unverified
- Server rate-limited: no
- Parameters: 0
- Recommended policy verdict: Rate-limited

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

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

## Why retry_job is rated High

Retrying a failed job triggers re-execution of that job in the queue. This is an operational action that causes external side effects depending on what the job does, classifying it as Execute. It's not purely destructive or financial, but it does trigger processing that could have downstream consequences.

From the tool's own definition: "Retry a failed job"

## Use case

AI agents invoke retry_job to trigger actions in BullMQ MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.

## Recommended policy (PolicyLayer)

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

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "retry_job": {
      "limits": [
        {
          "counter": "retry_job_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}
```

## 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
- `remove_job` — Destructive — https://policylayer.com/tools/adamhancock-bullmq-mcp/remove-job.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
- `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