Create a Gmail draft. Returns {id, message: {...}}.
AI agents use gmail_draft_create 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 a new Gmail draft message, which is a reversible write operation. It does not delete, execute code, move money, or trigger external side effects beyond Gmail's internal draft storage. While drafts can be deleted, the creation itself is non-destructive.
From the tool's definition Tool name 'gmail_draft_create' and description explicitly state it 'Create[s] a Gmail draft'. Creating a draft is a reversible write operation that modifies Gmail state by adding new data.
Attacks that exploit this kind of access
Create a Gmail draft. Returns {id, message: {...}}. 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_draft_create: 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_draft_create 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_draft_create 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_draft_create. 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_draft_create is provided by the Google Workspace MCP server (rajool/google-workspace-mcp). 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 →