AI agents call get_summary to retrieve information from Inbox without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool only queries and returns aggregate data about the inbox state without creating, modifying, deleting, or executing any operations. It has minimal blast radius if misused by an AI agent—the worst outcome is exposure of email metadata counts. No financial, destructive, or execution-related risks are present.
From the tool's definition Tool retrieves inbox statistics (total messages, unread count, messages from last 7 days) with no modification or deletion capability. The verb 'get' and the read-only nature of statistical queries align with the Read category.
Attacks that exploit this kind of access
Get inbox statistics: total messages, unread count, and messages from the last 7 days. It is categorised as a Read tool in the Inbox MCP Server, which means it retrieves data without modifying state.
Register the Inbox MCP server in PolicyLayer and add a rule for get_summary: 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 Inbox. Nothing to install.
get_summary 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_summary 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_summary. 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_summary is provided by the Inbox MCP server (p-w-4-z/inbox-mcp). 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 →