AI agents use reply_email to create or update resources in Email — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Email environment.
Replying to an email sends an outbound message on behalf of the user, which is a write/send operation. While it could be categorized as Execute (triggering external communication), the core action is composing and sending data. The blast radius is high because a misused reply could send sensitive, embarrassing, or malicious content to real recipients from the user's actual email account with no easy recall.
From the tool's definition 'reply_email' - replying to an email creates a new outbound message; description truncated but name clearly indicates sending a reply
Attacks that exploit this kind of access
Reply to an email. The. It is categorised as a Write tool in the Email MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Email MCP server in PolicyLayer and add a rule for reply_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 Email. Nothing to install.
reply_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 reply_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 reply_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.
reply_email is provided by the Email MCP server (kerodkibatu/email-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 →