get_email
AI agents call get_email 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 email content without side effects. The server is explicitly designed for read-only access to Fastmail, and get_email fits the Read category pattern of fetching existing data. No write, execute, destructive, or financial operations are possible. Severity is low because email data access, while sensitive, does not enable agent actions beyond viewing existing information.
From the tool's definition Server description explicitly states 'read-only access' and 'retrieving full email content' via JMAP API. Tool name 'get_email' and context of sibling tools (list_mailboxes, search_emails) indicate data retrieval with no modification or deletion capability.
Attacks that exploit this kind of access
get_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: 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 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 Fastmail MCP Server MCP server (nova-3951/fastmail-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 →