send_email_with_attachment · Gmail MCP Server MCP

WHAT IT DOES

What send_email_with_attachment does on Gmail MCP Server

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

WHY IT NEEDS A POLICY

Why send_email_with_attachment needs a policy

Sending emails is a Write operation—it creates new email messages and transmits them, modifying external email state irreversibly from the recipient's perspective. Severity is high because unauthorized sending could impersonate the account holder, spread malware via attachments, or facilitate phishing/social engineering at scale.

From the tool's definition Tool name 'send_email_with_attachment' indicates creation and transmission of emails with attachments. Server description confirms 'sending' emails is a core capability. No description provided for this specific tool.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

send_email_with_attachment Rate-limited

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

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "send_email_with_attachment": {
      "limits": [
        {
          "counter": "send_email_with_attachment_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 Gmail MCP Server, so you can run agents against it safely.

FAQ

Questions about send_email_with_attachment

What does the send_email_with_attachment tool do? +

send_email_with_attachment. It is categorised as a Write tool in the Gmail MCP Server 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_attachment? +

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

What risk level is send_email_with_attachment? +

send_email_with_attachment 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_attachment? +

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

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

send_email_with_attachment is provided by the Gmail MCP Server MCP server (xiangwanggithub/gmail-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.