Critical Risk →

del_mail

del_mail

How to control del_mail ↓

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

Critical Risk

The prefix 'del_' consistently indicates deletion across this server (cf. 'del_post'). Deleting mail is typically irreversible, making this Destructive. Confidence is slightly reduced due to empty description, but naming convention and context strongly support this classification.

From the tool's definition Tool name 'del_mail' strongly implies deletion of mail/messages. The server description mentions mailbox operations.

Documented attack patterns abuse exactly the kind of access del_mail gives an agent:

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

policy.json
{
  "version": "1",
  "default": "deny",
  "hide": [
    "del_mail"
  ]
}

del_mail 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 PTT 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.

Go deeper

What does the del_mail tool do? +

del_mail. It is categorised as a Destructive tool in the PTT 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 del_mail? +

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

What risk level is del_mail? +

del_mail 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 del_mail? +

Yes. Add a rate_limit block to the del_mail 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 del_mail completely? +

Set action: deny in the PolicyLayer policy for del_mail. 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 del_mail? +

del_mail is provided by the PTT MCP Server MCP server (pyptt/ptt_mcp_server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every PTT MCP Server tool call.

Deterministic rules across all 26 PTT MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

26 PTT MCP Server tools catalogued and risk-classified — across an index of 42,500+ 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.