move_failed_jobs_to_dlq

Move failed jobs to a dead letter queue with TTL. Designed for cleaning up old failed jobs that have been manually resolved.

SERVERBullMQ MCP Server SOURCEadamhancock/bullmq-mcp

Medium RISK CLASS

Category Write

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/move-failed-jobs-to-dlq.md

WHAT IT DOES

What move_failed_jobs_to_dlq does on BullMQ MCP Server

AI agents use move_failed_jobs_to_dlq to create or update resources in BullMQ MCP Server, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your BullMQ MCP Server environment.

RISK

Why move_failed_jobs_to_dlq is rated Medium

This tool creates or modifies data (job state and queue membership) in a reversible manner. While it moves jobs rather than deleting them, it changes their queue assignment and potentially their TTL settings. This is Write-category because the operation is reversible (jobs can be moved back or recovered from the DLQ), distinguishing it from Destructive.

From the tool's definition Tool description states it 'Move[s] failed jobs to a dead letter queue' - this modifies the state and location of job data by transferring them between queues, which is a reversible write operation.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

move_failed_jobs_to_dlq Rate-limited

move_failed_jobs_to_dlq stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "move_failed_jobs_to_dlq": {
      "limits": [
        {
          "counter": "move_failed_jobs_to_dlq_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

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

FAQ

Questions about move_failed_jobs_to_dlq

What does the move_failed_jobs_to_dlq tool do? +

Move failed jobs to a dead letter queue with TTL. Designed for cleaning up old failed jobs that have been manually resolved. It is categorised as a Write tool in the BullMQ MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on move_failed_jobs_to_dlq? +

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

move_failed_jobs_to_dlq is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit move_failed_jobs_to_dlq? +

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

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

move_failed_jobs_to_dlq 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 →

Across the catalogue

move-task on Kanban MCP Server → The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →