retry_job

Retry a failed job

SERVERBullMQ MCP Server SOURCEadamhancock/bullmq-mcp

High RISK CLASS

Category Execute

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/adamhancock-bullmq-mcp/retry-job.md

WHAT IT DOES

What retry_job does on BullMQ MCP Server

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.

RISK

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 definition Retry a failed job

Attacks that exploit this kind of access

RECOMMENDED RULE

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

retry_job Rate-limited

retry_job stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

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

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

FAQ

Questions about retry_job

What does the retry_job tool do? +

Retry a failed job. It is categorised as a Execute tool in the BullMQ MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on retry_job? +

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

retry_job is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit retry_job? +

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

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

retry_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 → High-risk tools on this server →

Across the catalogue

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

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →