send_email_with_attachments · MCP Outlook MCP: Risk & Policy

WHAT IT DOES

What send_email_with_attachments does on MCP Outlook

AI agents use send_email_with_attachments to create or update resources in MCP Outlook — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your MCP Outlook environment.

WHY IT NEEDS A POLICY

Why send_email_with_attachments needs a policy

Sending an email with attachments creates and transmits a message to one or more recipients. This is a Write operation (creates/modifies data reversibly) rather than Execute because it doesn't run arbitrary code or trigger unpredictable external operations beyond the email transmission itself. It's not Financial, Destructive, or Read.

From the tool's definition Tool name 'send_email_with_attachments' indicates creation and transmission of email messages. Parent server description states the tool enables AI assistants to 'manage Microsoft Outlook emails' via COM automation.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

send_email_with_attachments Rate-limited

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

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "send_email_with_attachments": {
      "limits": [
        {
          "counter": "send_email_with_attachments_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches MCP Outlook, so you can run agents against it safely.

FAQ

Questions about send_email_with_attachments

What does the send_email_with_attachments tool do? +

send_email_with_attachments. It is categorised as a Write tool in the MCP Outlook MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on send_email_with_attachments? +

Register the MCP Outlook MCP server in PolicyLayer and add a rule for send_email_with_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 MCP Outlook. Nothing to install.

What risk level is send_email_with_attachments? +

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

Can I rate-limit send_email_with_attachments? +

Yes. Add a rate_limit block to the send_email_with_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.

How do I block send_email_with_attachments completely? +

Set action: deny in the PolicyLayer policy for send_email_with_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.

What MCP server provides send_email_with_attachments? +

send_email_with_attachments is provided by the MCP Outlook MCP server (vince1024/outlook-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.