sendDraft
Sends an existing Gmail draft. After sending, the draft is removed and the message appears in Sent. This is the second half of the compose-review-send flow that pairs with createDraft.
This record as markdown: /tools/a-bonus-google-docs-mcp/senddraft.md
What sendDraft does on Claude MCP x Google Docs
AI agents use sendDraft to create or update resources in Claude MCP x Google Docs, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Claude MCP x Google Docs environment.
Why sendDraft is rated Medium
This tool modifies state by sending a prepared message, but does not irreversibly destroy data or cause financial harm. However, it does trigger an external communication with potential side effects (message delivery to recipients), making it more than a simple data update.
From the tool's definition Sends an existing Gmail draft, which is a reversible write operation. The message moves from Drafts to Sent folder—data is transmitted but not destroyed, and the action is technically reversible (the sent email can be deleted or unsent where supported).
Attacks that exploit this kind of access
The rule that runs sendDraft safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Claude MCP x Google Docs, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For sendDraft, this is the rule to start with:
sendDraft 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Claude MCP x Google Docs, apply this rule, and every sendDraft call is checked against it from then on.
Questions about sendDraft
Sends an existing Gmail draft. After sending, the draft is removed and the message appears in Sent. This is the second half of the compose-review-send flow that pairs with createDraft. It is categorised as a Write tool in the Claude MCP x Google Docs MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Claude MCP x Google Docs MCP server in PolicyLayer and add a rule for sendDraft: 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 Claude MCP x Google Docs. Nothing to install.
sendDraft 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 sendDraft 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 sendDraft. 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.
sendDraft is provided by the Claude MCP x Google Docs MCP server (a-bonus/google-docs-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Claude MCP x Google Docs, and thousands of servers like it.
This server
Across the catalogue