Purpose: Show agent presence in the Resend dashboard editor. Users will see an agent avatar while connected. When to use: - To signal to dashboard users that an AI agent is working on the content outside of compose workflows - Not needed before compose-broadcast or compose-template — get-tiptap-j...
AI agents use connect-to-editor 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 performs a reversible state modification—it establishes a connection session that signals presence in the Resend dashboard editor. While it doesn't directly create or modify email content or contacts, it does write/establish a session state (connection token, room ID) in the dashboard.
From the tool's definition Tool creates a connection state ('Show agent presence', 'Returns: Connection token and room ID'), modifying the dashboard's display and session state by adding an agent avatar/indicator.
Documented attack patterns abuse exactly the kind of access connect-to-editor 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 connect-to-editor:
{
"version": "1",
"default": "deny",
"tools": {
"connect-to-editor": {
"limits": [
{
"counter": "connect-to-editor_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}connect-to-editor 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: Show agent presence in the Resend dashboard editor. Users will see an agent avatar while connected. When to use: - To signal to dashboard users that an AI agent is working on the content outside of compose workflows - Not needed before compose-broadcast or compose-template — get-tiptap-json-content connects automatically, and compose tools disconnect when done. Returns: Connection token and room ID. 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 connect-to-editor: 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.
connect-to-editor 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 connect-to-editor 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 connect-to-editor. 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.
connect-to-editor 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.