Remove agent presence from the Resend dashboard editor. Call this when done editing.
AI agents use disconnect-from-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 state modification (removing agent presence from a dashboard session) that is reversible and has minimal blast radius. It does not execute external commands, delete data, move money, or perform destructive operations. It fits the Write category as a session state update, though with low severity since the impact is confined to UI session state with no data or system consequences.
From the tool's definition The tool 'disconnects' the agent from the editor by removing 'agent presence', which modifies session state in the Resend dashboard. It is a reversible operation (the agent can reconnect later) with no permanent data deletion or financial impact.
Documented attack patterns abuse exactly the kind of access disconnect-from-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 disconnect-from-editor:
{
"version": "1",
"default": "deny",
"tools": {
"disconnect-from-editor": {
"limits": [
{
"counter": "disconnect-from-editor_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}disconnect-from-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.
Remove agent presence from the Resend dashboard editor. Call this when done editing. 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 disconnect-from-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.
disconnect-from-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 disconnect-from-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 disconnect-from-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.
disconnect-from-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.