email_save_draft
Save an email draft to Gmail. Use before sending, or when you want to review/finish later.
This record as markdown: /tools/0xcjt-templonixlite/email-save-draft.md
What email_save_draft does on Templonix Lite MCP Server
AI agents use email_save_draft to create or update resources in Templonix Lite MCP Server, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Templonix Lite MCP Server environment.
Why email_save_draft is rated Medium
This tool creates/modifies data (email drafts) in a user's Gmail account without destructive or irreversible effects. It does not execute external commands, delete data, or commit financial actions. The severity is medium because unauthorized draft creation could enable phishing/spam composition and represent mild account compromise, but drafts themselves cause no immediate harm until sent.
From the tool's definition Tool explicitly performs 'Save an email draft' action - creates or stores a new email object in Gmail without sending it. Reversible operation (draft can be deleted or overwritten).
Attacks that exploit this kind of access
The rule that runs email_save_draft safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Templonix Lite MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For email_save_draft, this is the rule to start with:
email_save_draft 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 Templonix Lite MCP Server, apply this rule, and every email_save_draft call is checked against it from then on.
Questions about email_save_draft
Save an email draft to Gmail. Use before sending, or when you want to review/finish later. It is categorised as a Write tool in the Templonix Lite MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Templonix Lite MCP Server MCP server in PolicyLayer and add a rule for email_save_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 Templonix Lite MCP Server. Nothing to install.
email_save_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 email_save_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 email_save_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.
email_save_draft is provided by the Templonix Lite MCP Server MCP server (0xcjt/templonixlite). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Templonix Lite MCP Server, and thousands of servers like it.
This server
Across the catalogue