add_job_log

Add a log entry to a job

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/add-job-log.md

WHAT IT DOES

What add_job_log does on BullMQ MCP Server

AI agents use add_job_log 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 add_job_log is rated Medium

This tool creates new log entries within a job object in Redis via BullMQ. While logs are typically append-only and individual entries cannot be easily deleted, the operation itself is not destructive (the job and existing logs remain intact).

From the tool's definition add_job_log modifies job state by appending a log entry to an existing job, as confirmed by the tool name 'add_job_log' and description 'Add a log entry to a job'. This is a reversible data creation operation.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

add_job_log Rate-limited

add_job_log 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": {
    "add_job_log": {
      "limits": [
        {
          "counter": "add_job_log_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 add_job_log call is checked against it from then on.

FAQ

Questions about add_job_log

What does the add_job_log tool do? +

Add a log entry to a job. 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 add_job_log? +

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

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

Can I rate-limit add_job_log? +

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

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

add_job_log 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

add-tag on Kanban MCP Server →kb_add on Persistent Kb → The MCP Attack Database →

Guides

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