AI agents call company_a2a_inbox to retrieve information from Wmux without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves/queries messages from an inbox. It reads incoming agent messages without creating, modifying, or deleting data. Pure read operation with minimal blast radius.
From the tool's definition Check your inbox for incoming messages from other agents
Attacks that exploit this kind of access
Check your inbox for incoming messages from other agents. It is categorised as a Read tool in the Wmux MCP Server, which means it retrieves data without modifying state.
Register the Wmux MCP server in PolicyLayer and add a rule for company_a2a_inbox: 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 Wmux. Nothing to install.
company_a2a_inbox 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 company_a2a_inbox 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 company_a2a_inbox. 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.
company_a2a_inbox is provided by the Wmux MCP server (openwong2kim/wmux). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
company_a2a_inbox is one line of Wmux's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →