add_job

What add_job does on BullMQ MCP Server

AI agents use add_job 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.

Why add_job is rated Medium

Adding a job to a queue creates a new record in the BullMQ system. This is reversible (the job can be removed, failed, or cleaned up), making it a Write operation rather than Execute (which would require actual code execution) or Destructive (which would be irreversible). The severity is medium because misuse could flood queues with unwanted jobs, but the effect is reversible and limited to queue state.

From the tool's definition Tool is named 'add_job' and described as 'Add a new job to the queue'. The sibling tools include destructive operations (clean_queue, drain_queue) and read operations (get_job, get_jobs, list_queues), establishing that this server manages job queues.

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

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

Questions about add_job