AI agents use save_draft to create or update resources in Gmail — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Gmail environment.
This tool creates or modifies data (draft emails) reversibly without executing code or triggering external operations. It is not destructive since drafts can be edited or deleted. It is not financial. While it is part of an email system, the tool itself only creates drafts—it does not send messages or access sensitive data for retrieval purposes. Write is the appropriate category for reversible state modifications.
From the tool's definition Tool description states 'Save an email as a draft', which creates a new email object (reversibly). The sibling tools 'send' operations and 'delete' operations indicate this server manages email state; saving a draft is a write operation that modifies mailbox…
Attacks that exploit this kind of access
Save an email as a draft. All fields except body are optional, allowing partial drafts. It is categorised as a Write tool in the Gmail MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Gmail MCP server in PolicyLayer and add a rule for save_draft: 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. Nothing to install.
save_draft 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 save_draft 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 save_draft. 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.
save_draft is provided by the Gmail MCP server (ndungukamami-sketch/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 →