AI agents use reply_message to create or update resources in Mail — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Mail environment.
Replying to messages creates and modifies email data (composing a new message, appending to conversation thread) but does not irreversibly destroy data. This is a Write operation. Severity is medium because an agent could impersonate the user, send unwanted communications, or leak sensitive information via unintended recipients, but the action remains reversible (deleted/withdrawn). Confidence is lowered slightly (0.
From the tool's definition Tool name 'reply_message' in an IMAP/SMTP email server context; sibling tools include 'send_message' pattern operations (forward_message, daily_digest).
Attacks that exploit this kind of access
reply_message. It is categorised as a Write tool in the Mail MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Mail MCP server in PolicyLayer and add a rule for reply_message: 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 Mail. Nothing to install.
reply_message 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_message 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_message. 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_message is provided by the Mail MCP server (kpihx/mail-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 →