Remove a segment by ID from Resend. Before using this tool, you MUST double-check with the user that they want to remove this segment. Reference the NAME of the segment when double-checking, and warn the user that removing a segment is irreversible. You may only use this tool if the user explicit...
AI agents call remove-segment to permanently remove resources in Email Sending MCP — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool permanently deletes a segment from the Resend email service. Segments are organizational data structures used for email list management and targeting. Once removed, the segment cannot be recovered. The tool's own documentation emphasizes the irreversible nature and mandates user confirmation, which further confirms the destructive category.
From the tool's definition Tool description explicitly states 'Remove a segment by ID from Resend' and warns that 'removing a segment is irreversible'. The use of 'remove' combined with the irreversible nature of the operation classifies this as destructive.
Documented attack patterns abuse exactly the kind of access remove-segment 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 remove-segment:
{
"version": "1",
"default": "deny",
"hide": [
"remove-segment"
]
}remove-segment disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.
Free to start. No card required.
Remove a segment by ID from Resend. Before using this tool, you MUST double-check with the user that they want to remove this segment. Reference the NAME of the segment when double-checking, and warn the user that removing a segment is irreversible. You may only use this tool if the user explicitly confirms they want to remove the segment after you double-check. It is categorised as a Destructive tool in the Email Sending MCP MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Email Sending MCP server in PolicyLayer and add a rule for remove-segment: 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.
remove-segment is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the remove-segment 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 remove-segment. 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.
remove-segment 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.