Create a Gmail draft. Returns draft_id.
AI agents use draft_email to create or update resources in Nexus Core — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Nexus Core environment.
This tool creates a new email draft in Gmail without sending it, which is a reversible modification operation. It does not execute code, delete data, or move money. The severity is medium because while drafts can be deleted, if an AI agent maliciously creates many drafts or composes sensitive/harmful content in draft form, it could cause disruption or expose private information.
From the tool's definition Create a Gmail draft. Returns draft_id. The tool creates a new email draft, which is reversible by deletion, and does not send or permanently modify existing data.
Attacks that exploit this kind of access
Create a Gmail draft. Returns draft_id. It is categorised as a Write tool in the Nexus Core MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Nexus Core MCP server in PolicyLayer and add a rule for draft_email: 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 Nexus Core. Nothing to install.
draft_email 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 draft_email 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 draft_email. 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.
draft_email is provided by the Nexus Core MCP server (noumenon-ai/nexus-core). 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 →