Send an email message to specified recipients. Note the mechanics of the raw parameter.
AI agents use send_message 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.
Sending emails is a reversible write action (messages can be unsent within brief windows, or deleted/retracted in some mail systems). However, it carries high severity because an AI agent with unconstrained access could spam large recipient lists, impersonate users, or send phishing messages at scale.
From the tool's definition Tool name is 'send_message' and description states it will 'Send an email message to specified recipients.' This is a write operation that creates a new message and transmits it.
Attacks that exploit this kind of access
Send an email message to specified recipients. Note the mechanics of the raw parameter. 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_message: 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_message 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_message 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_message. 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_message is provided by the Gmail MCP Server MCP server (nk900600/gmail-mcp). 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 →