Create a new email draft in Gmail. The draft is saved but NOT sent automatically. Args: - to (string[]): Array of recipient email addresses (required) - subject (string): Email subject line - body (string): Email body content (plain text or HTML depending on content_type) - content_type (string, ...
AI agents use gmail_create_draft to create or update resources in Google Workspace — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Google Workspace environment.
This tool creates new email drafts as data artifacts in Gmail. While drafts are not sent automatically (reducing immediate impact), they are persistent modifications to the user's mailbox state. This is reversible (drafts can be deleted), so it does not qualify as Destructive. It does not execute arbitrary code or trigger external operations beyond creating a draft object, so Execute does not apply.
From the tool's definition Tool name 'gmail_create_draft' and description 'Create a new email draft in Gmail. The draft is saved but NOT sent automatically.' explicitly indicates creation of email drafts, which are stored data objects.
Documented attack patterns abuse exactly the kind of access gmail_create_draft gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Google Workspace, and nothing reaches the server without passing your rules. This is the rule we recommend for gmail_create_draft:
{
"version": "1",
"default": "deny",
"tools": {
"gmail_create_draft": {
"limits": [
{
"counter": "gmail_create_draft_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}gmail_create_draft stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Create a new email draft in Gmail. The draft is saved but NOT sent automatically. Args: - to (string[]): Array of recipient email addresses (required) - subject (string): Email subject line - body (string): Email body content (plain text or HTML depending on content_type) - content_type (string, optional): MIME content type -. It is categorised as a Write tool in the Google Workspace MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Google Workspace MCP server in PolicyLayer and add a rule for gmail_create_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 Google Workspace. Nothing to install.
gmail_create_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 gmail_create_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 gmail_create_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.
gmail_create_draft is provided by the Google Workspace MCP server (everyinc/google-workspace-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Google Workspace, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
34 Google Workspace tools catalogued and risk-classified — across an index of 43,000+ MCP servers.