Critical Risk →

delete-smtp-config

Delete an SMTP configuration

How to control delete-smtp-config ↓

What delete-smtp-config does on SMTP MCP Server

AI agents call delete-smtp-config to permanently remove resources in SMTP MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Critical Risk

Why delete-smtp-config needs a policy

Deleting an SMTP configuration is an irreversible action that cannot be undone without manual reconfiguration. This breaks email sending capabilities for any templates or processes dependent on that configuration. While not directly financial or involving user data deletion, it causes significant operational disruption and fits the Destructive category for its irreversible nature.

From the tool's definition Tool name 'delete-smtp-config' explicitly performs a delete operation on SMTP configurations. The verb 'delete' indicates irreversible removal of data.

Documented attack patterns abuse exactly the kind of access delete-smtp-config gives an agent:

How to control delete-smtp-config

PolicyLayer is an MCP gateway — it sits between your AI agents and SMTP MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for delete-smtp-config:

policy.json
{
  "version": "1",
  "default": "deny",
  "hide": [
    "delete-smtp-config"
  ]
}

delete-smtp-config disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.

  1. Create a free account and register SMTP MCP Server — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
RESTRICT THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about delete-smtp-config

What does the delete-smtp-config tool do? +

Delete an SMTP configuration. It is categorised as a Destructive tool in the SMTP MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on delete-smtp-config? +

Register the SMTP MCP Server MCP server in PolicyLayer and add a rule for delete-smtp-config: 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 SMTP MCP Server. Nothing to install.

What risk level is delete-smtp-config? +

delete-smtp-config is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit delete-smtp-config? +

Yes. Add a rate_limit block to the delete-smtp-config 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.

How do I block delete-smtp-config completely? +

Set action: deny in the PolicyLayer policy for delete-smtp-config. 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.

What MCP server provides delete-smtp-config? +

delete-smtp-config is provided by the SMTP MCP Server MCP server (samihalawa/mcp-server-smtp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every SMTP MCP Server tool call.

Start from SMTP MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

Free to start. No card required.

11 SMTP MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.