AI agents use prepare_send_email 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.
The tool creates or modifies email content reversibly before sending, fitting the Write category. Severity is medium rather than high because: (1) the tool requires explicit confirmation before sending, (2) email is generally reversible to some degree (can be unsent in many systems shortly after sending), and (3) the blast radius is limited to communications rather than system-level or financial impacts.
From the tool's definition Tool name is 'prepare_send_email' and description states it 'Prepare email for sending'. This involves composing/creating email content (Write action).
Attacks that exploit this kind of access
✅ SAFE: Prepare email for sending - shows preview and requires confirmation. 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 prepare_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 Google. Nothing to install.
prepare_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 prepare_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 prepare_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.
prepare_send_email 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 →