fetch_inbox_product
AI agents call fetch_inbox_product to retrieve information from MCP Agent Mail without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool appears designed to retrieve inbox messages for a specific product in a multi-agent coordination system. Fetching or retrieving data is a read operation with no side effects. Even in a multi-agent environment, reading message history poses minimal risk—no data is modified, deleted, or executed. The low severity reflects that this is a passive data retrieval operation.
From the tool's definition Tool name 'fetch_inbox' (from sibling tools context) indicates retrieval of messages/inbox data with 'fetch' being a read operation. The 'product' suffix suggests filtering or scoping that retrieval. Description is empty, which lowers confidence slightly.
Attacks that exploit this kind of access
fetch_inbox_product. It is categorised as a Read tool in the MCP Agent Mail MCP Server, which means it retrieves data without modifying state.
Register the MCP Agent Mail MCP server in PolicyLayer and add a rule for fetch_inbox_product: 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 Agent Mail. Nothing to install.
fetch_inbox_product 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 fetch_inbox_product 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 fetch_inbox_product. 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.
fetch_inbox_product is provided by the MCP Agent Mail MCP server (omelchmichael/mcp_agent_mail). 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 →