Download and save email attachments to local file system. Can save a single attachment by index or all attachments. Auto-connects if not already connected.
AI agents use save_attachment to create or update resources in Mcp Mail Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Mcp Mail Server environment.
This tool creates or modifies data on the file system by writing attachment contents to disk. While not immediately destructive (data is not deleted), it is a Write operation that persists new files.
From the tool's definition Tool description states "Download and save email attachments to local file system," which creates new files on the local system.
Attacks that exploit this kind of access
Download and save email attachments to local file system. Can save a single attachment by index or all attachments. Auto-connects if not already connected. It is categorised as a Write tool in the Mcp Mail Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Mcp Mail Server MCP server in PolicyLayer and add a rule for save_attachment: 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 Mcp Mail Server. Nothing to install.
save_attachment 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 save_attachment 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 save_attachment. 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.
save_attachment is provided by the Mcp Mail Server MCP server (mcp-mail-server). 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 →