AI agents use update_email to create or update resources in Eml — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Eml environment.
The tool modifies (write operation) an existing email draft rather than deleting it (Destructive) or executing arbitrary code (Execute). The modification is reversible and limited to draft emails. Severity is medium because email modifications can cause confusion or unwanted message changes, but the impact is constrained to drafts and the operation is reversible.
From the tool's definition Tool description states 'Modify an existing .eml draft and re-open it', and the server manages email archives with drafts that can be written to.
Attacks that exploit this kind of access
Modify an existing .eml draft and re-open it. It is categorised as a Write tool in the Eml MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Eml MCP server in PolicyLayer and add a rule for update_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.
update_email is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the update_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 update_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.
update_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 →