save_attachment
Saves an attachment from an email to disk. Pass account= (and mailbox= if known, both from list_emails/search_emails) so the lookup targets one account instead of scanning all of them.
This record as markdown: /tools/com-local-mcp-local-mcp/save-attachment.md
What save_attachment does on Local
AI agents use save_attachment to create or update resources in Local, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Local environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
account | string | — | |
confirm | boolean | — | |
mailbox | string | — | |
message_id | string | Yes | |
destination | string | — | |
attachment_name | string | Yes |
Parameters from the server's own tool schema.
Why save_attachment is rated Medium
This tool creates new files on disk by extracting and persisting email attachments. While it does not delete or overwrite existing data (hence not Destructive), and does not move money (hence not Financial), it does modify the filesystem state by adding new files. This is a Write operation.
From the tool's definition Tool name 'save_attachment' and description 'Saves an attachment from an email to disk' indicate creation/writing of files to the user's filesystem.
Risk signalsAccepts file system path (destination)
Attacks that exploit this kind of access
The rule that runs save_attachment safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Local, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For save_attachment, this is the rule to start with:
save_attachment stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Local, apply this rule, and every save_attachment call is checked against it from then on.
Questions about save_attachment
Saves an attachment from an email to disk. Pass account= (and mailbox= if known, both from list_emails/search_emails) so the lookup targets one account instead of scanning all of them. It is categorised as a Write tool in the Local MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
save_attachment accepts 6 parameters: account, confirm, mailbox, message_id, destination, attachment_name. Required: message_id, attachment_name. The full parameter table on this page comes from the server's own tool schema.
Register the Local 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 Local. 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 Local MCP server (local-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Local, and thousands of servers like it.
This server
Across the catalogue