Create or update a RabbitMQ policy. Policies apply configurations to
AI agents use rmq_policy_set 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.
This tool creates or updates RabbitMQ policies, which are reversible modifications to system configuration. It does not delete data (would be Destructive), execute arbitrary code (would be Execute), or move money (would be Financial). The medium severity reflects that misconfigured policies could degrade message queue performance or availability, but changes are typically reversible through reconfiguration.
From the tool's definition Tool description states 'Create or update a RabbitMQ policy', which are write operations that modify configuration state in RabbitMQ.
Attacks that exploit this kind of access
Create or update a RabbitMQ policy. Policies apply configurations to. 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.
Register the RedisNexus MCP server in PolicyLayer and add a rule for rmq_policy_set: 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.
rmq_policy_set is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the rmq_policy_set 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.
Set action: deny in the PolicyLayer policy for rmq_policy_set. 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.
rmq_policy_set 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.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →