Get the full body content of a specific email
AI agents call get_email_body to retrieve information from FastMail 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 content without side effects. It falls under the Read category as it performs a straightforward data retrieval operation similar to 'get' or 'fetch' patterns. The severity is low because misuse would at worst expose already-existing email content the user has access to, with no ability to modify, delete, or trigger external operations.
From the tool's definition Tool name 'get_email_body' and description 'Get the full body content of a specific email' indicate retrieval of existing email data with no modification or deletion.
Attacks that exploit this kind of access
Get the full body content of a specific email. It is categorised as a Read tool in the FastMail MCP Server MCP Server, which means it retrieves data without modifying state.
Register the FastMail MCP Server MCP server in PolicyLayer and add a rule for get_email_body: 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 FastMail MCP Server. Nothing to install.
get_email_body 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_body 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_body. 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_body is provided by the FastMail MCP Server MCP server (jmhron/fastmailmcp). 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 →