Medium Risk

outlook_save_attachment

Saves attachments from an Outlook email to a folder.

Risk signalsAccepts file system path (path)

Part of the Local server.

outlook_save_attachment can modify Local data, with no limits today. PolicyLayer puts allow, deny, and rate-limit rules on every call. Live in minutes.

SECURE LOCAL →

Free to start. No card required.

AI agents use outlook_save_attachment to create or modify resources in Local. Write operations carry medium risk because an autonomous agent could trigger bulk unintended modifications. Rate limits prevent a single agent session from making hundreds of changes in rapid succession. Argument validation ensures the agent passes expected values.

Without a policy, an AI agent could call outlook_save_attachment repeatedly, creating or modifying resources faster than any human could review. PolicyLayer's rate limiting ensures write operations happen at a controlled pace, and argument validation catches malformed or unexpected inputs before they reach Local.

Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "outlook_save_attachment": {
      "limits": [
        {
          "counter": "outlook_save_attachment_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

See the full Local policy for all 108 tools.

Get this rule live on your own Local server in minutes. PolicyLayer enforces it on every call, before it runs.

ENFORCE ON MY LOCAL →

View all 108 tools →

These attack patterns abuse exactly the kind of access outlook_save_attachment gives an agent. Each links to the full case and the policy that stops it:

Browse the full MCP Attack Database →

Every attack above starts with a tool call. PolicyLayer checks each one against your policy first, so outlook_save_attachment only ever does what you allow.

SECURE LOCAL →

Other write tools across the catalogue. The same approach applies to each: rate-limit and validate the arguments.

What does the outlook_save_attachment tool do? +

Saves attachments from an Outlook email to a folder.. 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.

How do I enforce a policy on outlook_save_attachment? +

Register the Local MCP server in PolicyLayer and add a rule for outlook_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 outlook_save_attachment? +

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

Can I rate-limit outlook_save_attachment? +

Yes. Add a rate_limit block to the outlook_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 outlook_save_attachment completely? +

Set action: deny in the PolicyLayer policy for outlook_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 outlook_save_attachment? +

outlook_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.

Enforce policy on every Local tool call.

Deterministic rules across all 108 Local tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

4,600+ MCP servers and 31,000+ tools scanned and risk-classified.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.