Saves a draft reply to a specific email in the user
AI agents use save_draft_reply_to_gmail to create or update resources in Gmail MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Gmail MCP Server environment.
This tool creates/modifies email drafts reversibly—drafts can be edited, deleted, or discarded before sending. It does not send emails (which would be Execute/Financial), does not delete data irreversibly, and does not read/query data.
From the tool's definition Tool description states it "Saves a draft reply" which creates a new email draft artifact in Gmail. The sibling tool context (create_suggested_draft_reply, get_unread_emails) and server description confirm this operates on Gmail drafts via the Gmail API.
Attacks that exploit this kind of access
Saves a draft reply to a specific email in the user. It is categorised as a Write tool in the Gmail MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Gmail MCP Server MCP server in PolicyLayer and add a rule for save_draft_reply_to_gmail: 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 MCP Server. Nothing to install.
save_draft_reply_to_gmail 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_reply_to_gmail 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_reply_to_gmail. 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_reply_to_gmail is provided by the Gmail MCP Server MCP server (jbr90/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 →