AI agents use gmail_send_html_message to create or update resources in Google — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Google environment.
Sending email is a reversible write operation—the message can be recalled, deleted, or remedied by sending follow-up communications. However, it carries high severity because an AI agent sending emails without proper authorization could impersonate users, spam recipients, leak sensitive information, or damage relationships/reputation.
From the tool's definition Tool name 'gmail_send_html_message' and description 'Send an HTML Gmail message' indicate the tool creates and sends email messages. This is a write operation that modifies Gmail state by adding a new message to the sent folder and delivering it to recipients.
Attacks that exploit this kind of access
Send an HTML Gmail message. It is categorised as a Write tool in the Google MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Google MCP server in PolicyLayer and add a rule for gmail_send_html_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 Google. Nothing to install.
gmail_send_html_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 gmail_send_html_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 gmail_send_html_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.
gmail_send_html_message is provided by the Google MCP server (robcerda/google-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 →