Send an email with optional CC/BCC
AI agents use send_email 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.
Although the server description emphasizes 'safety-first design that prevents accidental sends by default,' the send_email tool itself performs an irreversible action—transmitting email to external recipients. This is categorized as Write rather than Execute because it is a direct communication action with specific side effects (delivery to named recipients), not arbitrary code execution.
From the tool's definition Tool name 'send_email' with description 'Send an email with optional CC/BCC' directly performs email transmission, which creates and sends a message that reaches recipients' inboxes.
Attacks that exploit this kind of access
Send an email with optional CC/BCC. 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.
Register the Gmail MCP Server MCP server in PolicyLayer and add a rule for send_email: 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.
send_email 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 send_email 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 send_email. 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.
send_email is provided by the Gmail MCP Server MCP server (javiezpeleta/gmail-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →