Get detailed content of a specific email by its number from the last listing
AI agents call get_email_by_number to retrieve information from MCP-server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries email data ('Get detailed content') with no side effects. It is a read-only operation that fetches an existing email by reference number. No data is created, modified, deleted, or sent. The blast radius is limited to information disclosure of emails the user has already accessed.
From the tool's definition Tool name 'get_email_by_number' and description 'Get detailed content of a specific email by its number from the last listing' indicate a retrieval operation that reads email content without modifying, deleting, or sending anything.
Attacks that exploit this kind of access
Get detailed content of a specific email by its number from the last listing. It is categorised as a Read tool in the MCP-server MCP Server, which means it retrieves data without modifying state.
Register the MCP-server MCP server in PolicyLayer and add a rule for get_email_by_number: 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-server. Nothing to install.
get_email_by_number 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_email_by_number 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_email_by_number. 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_email_by_number is provided by the MCP-server MCP server (prathapmahi/mcp-server). 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 →