email_draft
Create an email draft in a connected mailbox. The draft is saved but not sent.
This record as markdown: /tools/flowdot-llc-mcp-server/email-draft.md
What email_draft does on FlowDot MCP Server
AI agents use email_draft to create or update resources in FlowDot MCP Server, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your FlowDot MCP Server environment.
Why email_draft is rated Medium
This tool creates new data (email draft) in a connected mailbox, which is a reversible write operation. It does not execute code, delete data, move money, or trigger destructive actions. While email is sensitive data, the draft is not sent and remains in the user's mailbox, mitigating risk.
From the tool's definition Tool description states it will 'Create an email draft in a connected mailbox. The draft is saved but not sent.' The use of 'Create' and 'saved' indicates a reversible write operation that modifies mailbox state.
Attacks that exploit this kind of access
The rule that runs email_draft safely
PolicyLayer is an MCP gateway: it sits between your AI agents and FlowDot MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For email_draft, this is the rule to start with:
email_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 FlowDot MCP Server, apply this rule, and every email_draft call is checked against it from then on.
Questions about email_draft
Create an email draft in a connected mailbox. The draft is saved but not sent. It is categorised as a Write tool in the FlowDot MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the FlowDot MCP Server MCP server in PolicyLayer and add a rule for email_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 FlowDot MCP Server. Nothing to install.
email_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_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_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_draft is provided by the FlowDot MCP Server MCP server (flowdot-llc/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on FlowDot MCP Server, and thousands of servers like it.
This server
Across the catalogue