AI agents call get_email to retrieve information from Eml without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool performs a read-only operation—it parses and returns email content without creating, modifying, deleting, or executing any actions. While email content can be sensitive, the tool itself has no side effects and does not alter data. The severity is low because the blast radius of this tool being misused is limited to information disclosure rather than data loss or system compromise.
From the tool's definition Tool name is 'get_email' and description states 'Parse and return a single .eml file with full content'. This is a retrieval operation that queries and returns existing email data without modification.
Attacks that exploit this kind of access
Parse and return a single .eml file with full content. It is categorised as a Read tool in the Eml MCP Server, which means it retrieves data without modifying state.
Register the Eml MCP server in PolicyLayer and add a rule for get_email: 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 Eml. Nothing to install.
get_email 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 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. 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 is provided by the Eml MCP server (miguelripoll23/eml-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 →