Creates a draft email message from scratch in Gmail with specified recipient, subject, body, and optional CC recipients. Do NOT use this tool when you want to draft or send a REPLY to an existing message. This tool does NOT include any previous message content. Use the reply_gmail_email tool with...
AI agents use gmail_create_draft to create or update resources in MCP Google Workspace Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your MCP Google Workspace Server environment.
This tool creates new email drafts, which is a reversible write operation. A draft is not yet sent, so it does not execute external delivery or have permanent consequences.
From the tool's definition Tool description explicitly states it "Creates a draft email message" with specified recipient, subject, body, and CC recipients. The verb 'Creates' and the operational purpose of composing new email drafts indicates data creation.
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 MCP Google Workspace Server, 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.
Creates a draft email message from scratch in Gmail with specified recipient, subject, body, and optional CC recipients. Do NOT use this tool when you want to draft or send a REPLY to an existing message. This tool does NOT include any previous message content. Use the reply_gmail_email tool with send=false instead. It is categorised as a Write tool in the MCP Google Workspace Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the MCP Google Workspace Server 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 MCP Google Workspace Server. 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 MCP Google Workspace Server MCP server (j3k0/mcp-google-workspace). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from MCP Google Workspace Server, 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.
16 MCP Google Workspace Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.