Purpose: Set the TipTap JSON content of a template, enabling it to be edited visually in the Resend dashboard editor. Automatically connects and disconnects from the editor. Can also update metadata (subject, name) in the same call. This is the recommended way to set email content. Content set vi...
AI agents use compose-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 or modifies email template content and metadata (subject, name) in a reversible way. It does not send emails or delete data, making it a Write operation. Misuse could result in unintended email template content being set, but templates can be edited again, keeping severity at medium.
From the tool's definition Set the TipTap JSON content of a template...Can also update metadata (subject, name) in the same call
Documented attack patterns abuse exactly the kind of access compose-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 compose-template:
{
"version": "1",
"default": "deny",
"tools": {
"compose-template": {
"limits": [
{
"counter": "compose-template_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}compose-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.
Purpose: Set the TipTap JSON content of a template, enabling it to be edited visually in the Resend dashboard editor. Automatically connects and disconnects from the editor. Can also update metadata (subject, name) in the same call. This is the recommended way to set email content. Content set via compose-template can be visually edited by the user in the dashboard. Workflow: get-tiptap-json-content (with include_schema: true) → compose-template When to use: - After create-template, to set the email body - When the user wants to write, edit, or style email content - When the user wants to collaborate on the email in the dashboard editor Important: Always call get-tiptap-json-content first to retrieve the existing TipTap JSON, then build your changes on top of it. Skipping this will overwrite all existing content. Note: Switching between compose (TipTap) and update (raw HTML) modes is lossy — some content or formatting may be lost. If the template already has HTML content, ask the user before switching to compose mode. 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 compose-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.
compose-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 compose-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 compose-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.
compose-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.