AI agents call mail_attachments to retrieve information from Outpost without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves metadata about email attachments without modifying, deleting, or executing any operations. It is purely informational and poses minimal risk if misused by an AI agent.
From the tool's definition Tool name 'mail_attachments' and description 'List attachments for an email message' indicate a query/retrieval operation with no side effects.
Attacks that exploit this kind of access
List attachments for an email message. It is categorised as a Read tool in the Outpost MCP Server, which means it retrieves data without modifying state.
Register the Outpost MCP server in PolicyLayer and add a rule for mail_attachments: 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_attachments 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 mail_attachments 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_attachments. 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_attachments 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 →