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.

SERVERLocal SOURCElocal-mcp
Medium RISK CLASS
Category Write
Parameters 62 required
Recommended Rate-limitedsee the rule below
Registry record Grade F, identity unverified Pull the record →

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.

ParameterTypeRequiredDescription
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)

Questions about save_attachment

What does the save_attachment tool do? +

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.

What parameters does save_attachment accept? +

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.

How do I enforce a policy on save_attachment? +

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.

What risk level is save_attachment? +

save_attachment is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit save_attachment? +

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.

How do I block save_attachment completely? +

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.

What MCP server provides save_attachment? +

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.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Local's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.