Push a message to a queue. Requires the push_token for that queue. Default TTL is 24 hours; set ttl_seconds for a shorter or longer expiry (max 7 days). Limit: 1000 messages/queue/day.
Risk signalsAccepts raw HTML/template content (body)
Part of the CrabbitMQ server.
Free to start. No card required.
AI agents use push_message to create or modify resources in CrabbitMQ. Write operations carry medium risk because an autonomous agent could trigger bulk unintended modifications. Rate limits prevent a single agent session from making hundreds of changes in rapid succession. Argument validation ensures the agent passes expected values.
Without a policy, an AI agent could call push_message repeatedly, creating or modifying resources faster than any human could review. PolicyLayer's rate limiting ensures write operations happen at a controlled pace, and argument validation catches malformed or unexpected inputs before they reach CrabbitMQ.
Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.
{
"version": "1",
"default": "deny",
"tools": {
"push_message": {
"limits": [
{
"counter": "push_message_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
} See the full CrabbitMQ policy for all 6 tools.
These attack patterns abuse exactly the kind of access push_message gives an agent. Each links to the full case and the policy that stops it:
Other write tools across the catalogue. The same approach applies to each: rate-limit and validate the arguments.
Push a message to a queue. Requires the push_token for that queue. Default TTL is 24 hours; set ttl_seconds for a shorter or longer expiry (max 7 days). Limit: 1000 messages/queue/day.. It is categorised as a Write tool in the CrabbitMQ MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the CrabbitMQ MCP server in PolicyLayer and add a rule for push_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 CrabbitMQ. Nothing to install.
push_message 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 push_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 push_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.
push_message is provided by the CrabbitMQ MCP server (https://crabbitmq.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 6 CrabbitMQ tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
4,600+ MCP servers and 31,000+ tools scanned and risk-classified.