Get all queued MQTT messages without blocking
AI agents call get_queued_messages to retrieve information from Mcp Coordinator without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves/queries queued messages from an MQTT broker without side effects. It does not create, modify, delete, or execute operations — it only reads the current state of the message queue. The 'without blocking' clause indicates a non-destructive polling mechanism.
From the tool's definition Tool name is 'get_queued_messages' and description states 'Get all queued MQTT messages without blocking' — the verb 'get' and absence of any modification language indicate a read-only retrieval operation.
Attacks that exploit this kind of access
Get all queued MQTT messages without blocking. It is categorised as a Read tool in the Mcp Coordinator MCP Server, which means it retrieves data without modifying state.
Register the Mcp Coordinator MCP server in PolicyLayer and add a rule for get_queued_messages: 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 Mcp Coordinator. Nothing to install.
get_queued_messages is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_queued_messages 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 get_queued_messages. 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.
get_queued_messages is provided by the Mcp Coordinator MCP server (swoofer/mcp-coordinator). 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 →