Create a new exchange. Types: direct (exact routing key match), fanout (broadcast),
AI agents use rmq_exchange_create 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 new message queue exchanges, which is a reversible modification of infrastructure/configuration state. It does not execute arbitrary code, delete data, or move money. The severity is medium because misconfiguration could disrupt message routing in production systems, but the operation itself is reversible (the exchange can be deleted).
From the tool's definition Tool name 'rmq_exchange_create' and description 'Create a new exchange' indicate data creation capability. The description is cut off but clearly describes exchange configuration in a message queue system.
Attacks that exploit this kind of access
Create a new exchange. Types: direct (exact routing key match), fanout (broadcast),. 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_exchange_create: 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_exchange_create 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_exchange_create 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_exchange_create. 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_exchange_create 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 →