AI agents use mail_reply to create or update resources in Outpost — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Outpost environment.
Sending a reply to an email creates a new message and delivers it externally, which is a write/send operation. While it has external effects, it is not irreversible in the destructive sense nor financial. The blast radius is medium because an AI agent could send unintended replies to real recipients.
From the tool's definition Reply to an email in Outlook
Attacks that exploit this kind of access
Reply to an email in Outlook. It is categorised as a Write tool in the Outpost MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Outpost MCP server in PolicyLayer and add a rule for mail_reply: 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 Outpost. Nothing to install.
mail_reply 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 mail_reply 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 mail_reply. 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.
mail_reply is provided by the Outpost MCP server (signalclaude/outpost). 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 →