Purpose: Create an automation workflow that triggers on events and executes a sequence of steps. When to use: - User wants to set up automated email sequences (welcome series, drip campaigns, re-engagement) - User wants to automate actions based on events (update contacts, add to segments) Workfl...
AI agents use create-automation to create or update resources in Email Sending MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Email Sending MCP environment.
This tool creates new automation rules and workflows rather than reading data (Read), but does not immediately delete data (Destructive) or move money (Financial). While it executes automated sequences, the primary action is creating/configuring a workflow (Write).
From the tool's definition Tool creates automation workflows that trigger on events and execute sequences of steps, including automated email sequences, contact updates, and segment additions. This involves creating persistent configurations that modify system behavior and data state.
Documented attack patterns abuse exactly the kind of access create-automation gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Email Sending MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for create-automation:
{
"version": "1",
"default": "deny",
"tools": {
"create-automation": {
"limits": [
{
"counter": "create-automation_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}create-automation 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.
Free to start. No card required.
Purpose: Create an automation workflow that triggers on events and executes a sequence of steps. When to use: - User wants to set up automated email sequences (welcome series, drip campaigns, re-engagement) - User wants to automate actions based on events (update contacts, add to segments) Workflow: manage-events (create event, if needed) → list-templates (to get template IDs) → get-template (to check if template has. It is categorised as a Write tool in the Email Sending MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Email Sending MCP server in PolicyLayer and add a rule for create-automation: 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 Email Sending MCP. Nothing to install.
create-automation 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 create-automation 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 create-automation. 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.
create-automation is provided by the Email Sending MCP server (resend/resend-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 77 Email Sending MCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
77 Email Sending MCP tools catalogued and risk-classified — across an index of 42,500+ MCP servers.