mail_send_draft
AI agents use mail_send_draft to create or update resources in Hermes Google — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Hermes Google environment.
Sending a draft email is a reversible write operation—it creates a new sent message in Gmail. While the action cannot be undone perfectly (deletion is always possible but leaves traces), it does not permanently destroy data or move funds. It's more severe than a simple data creation because it involves external communication, but less severe than Destructive or Financial actions.
From the tool's definition Tool name 'mail_send_draft' indicates sending an email draft, which creates/transmits a message. Description is empty, limiting direct evidence, but the name clearly denotes a write operation that modifies Gmail state by converting a draft to a sent message.
Attacks that exploit this kind of access
mail_send_draft. It is categorised as a Write tool in the Hermes Google MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Hermes Google MCP server in PolicyLayer and add a rule for mail_send_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 Hermes Google. Nothing to install.
mail_send_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 mail_send_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 mail_send_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.
mail_send_draft is provided by the Hermes Google MCP server (jimmy-larsson/hermes-google). 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 →