Publish a message to an Anypoint MQ queue. Call mq_list_queues first to confirm the queueId.
AI agents invoke mq_send_message to trigger actions in Anypoint MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
Sending a message to a message queue is an external operation that can trigger downstream processing, workflows, or integrations. While it is not directly destructive or financial, it executes an action with potentially significant side effects depending on what consumes the queue. This fits Execute as the most severe applicable category — it is more than a write since it triggers external system behavior.
From the tool's definition 'Publish a message to an Anypoint MQ queue' — triggers an external messaging operation that delivers a message to a queue, causing downstream consumers to act on it.
Attacks that exploit this kind of access
Publish a message to an Anypoint MQ queue. Call mq_list_queues first to confirm the queueId. It is categorised as a Execute tool in the Anypoint MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Anypoint MCP Server MCP server in PolicyLayer and add a rule for mq_send_message: 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 Anypoint MCP Server. Nothing to install.
mq_send_message is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the mq_send_message 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 mq_send_message. 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.
mq_send_message is provided by the Anypoint MCP Server MCP server (sravannerella/mulesoft-mcp-server). 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 →