Create a new email template in Resend. Templates are created in draft status. Use publish-template to make them available for sending. Variables use triple-brace syntax in HTML: {{{VAR_NAME}}}. Workflow: create-template → get-tiptap-json-content (with include_schema: true) → compose-template → pu...
AI agents use create-template 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 email templates, which is a reversible data creation operation (Write category). It does not execute sending (that requires publish-template and compose-template), does not delete data (Destructive), and does not move money (Financial).
From the tool's definition Tool creates a new email template in Resend with 'draft status'. Description states 'Create a new email template' and references workflow with 'publish-template' to make templates 'available for sending', indicating this tool creates data that can be modified…
Documented attack patterns abuse exactly the kind of access create-template 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-template:
{
"version": "1",
"default": "deny",
"tools": {
"create-template": {
"limits": [
{
"counter": "create-template_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}create-template 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.
Create a new email template in Resend. Templates are created in draft status. Use publish-template to make them available for sending. Variables use triple-brace syntax in HTML: {{{VAR_NAME}}}. Workflow: create-template → get-tiptap-json-content (with include_schema: true) → compose-template → publish-template. Content options after creating: - compose-template (recommended): Sets TipTap content that the user can visually edit in the Resend dashboard. Use this when the user wants to collaborate on or refine the template in the editor. - update-template with html/text: Sets static HTML/text content. Use this only when the user explicitly wants to set raw HTML. Switching between compose and html/text modes is lossy — some content or formatting may be lost. Ask the user before switching. 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-template: 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-template 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-template 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-template. 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-template 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.