rmq_publish · RedisNexus MCP: Risk & Policy

WHAT IT DOES

What rmq_publish does on RedisNexus

AI agents use rmq_publish 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_publish needs a policy

Publishing messages to a queue is a reversible write operation—messages can be consumed and removed. It is not destructive (messages aren't permanently deleted), not financial, and not arbitrary code execution. However, it has medium severity because publishing malicious messages could trigger downstream automation, affect other services, or disrupt operations depending on what consumers process those messages.

From the tool's definition Tool name 'rmq_publish' and description 'Publish a message to an exchange with routing key' indicate the tool creates/sends messages to a message queue system (RabbitMQ). This is a write operation that modifies state by adding messages to a queue.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

rmq_publish Rate-limited

rmq_publish 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_publish": {
      "limits": [
        {
          "counter": "rmq_publish_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_publish

What does the rmq_publish tool do? +

Publish a message to an exchange with routing key. The exchange routes. 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_publish? +

Register the RedisNexus MCP server in PolicyLayer and add a rule for rmq_publish: 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_publish? +

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

Can I rate-limit rmq_publish? +

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

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

rmq_publish 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.