rmq_dead_letter · RedisNexus MCP: Risk & Policy

WHAT IT DOES

What rmq_dead_letter does on RedisNexus

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

WHY IT NEEDS A POLICY

Why rmq_dead_letter needs a policy

The tool performs infrastructure setup and management of dead letter queues, which creates or modifies queue configurations. While inspection is a read operation, the primary capability of 'managing' and 'setting up' DLQ infrastructure constitutes write-level impact. This is not Execute (no arbitrary code execution stated), not Destructive (configuration can be modified/reversed), and not Financial.

From the tool's definition Tool name 'rmq_dead_letter' and description 'Manage dead letter queues (DLQ). Set up DLQ infrastructure, inspect' indicate operations that create/configure queue infrastructure ('Set up DLQ infrastructure') and inspect message states.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

rmq_dead_letter Rate-limited

rmq_dead_letter 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": {
    "rmq_dead_letter": {
      "limits": [
        {
          "counter": "rmq_dead_letter_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches RedisNexus, so you can run agents against it safely.

FAQ

Questions about rmq_dead_letter

What does the rmq_dead_letter tool do? +

Manage dead letter queues (DLQ). Set up DLQ infrastructure, inspect. It is categorised as a Write tool in the RedisNexus MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on rmq_dead_letter? +

Register the RedisNexus MCP server in PolicyLayer and add a rule for rmq_dead_letter: 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 RedisNexus. Nothing to install.

What risk level is rmq_dead_letter? +

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

Can I rate-limit rmq_dead_letter? +

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

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

rmq_dead_letter is provided by the RedisNexus MCP server (rajkumar-madhu/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.