Critical Risk →

delete_snippet

Delete a snippet from the phone

How to control delete_snippet ↓

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

Critical Risk

Deleting a snippet removes data that cannot be recovered without manual backup. This is a destructive operation that permanently removes information from the user's phone. While not as critical as financial or system-level destruction, it causes irreversible data loss and represents a high-severity risk if an AI agent misuses it (e.g., deleting important snippets without authorization).

From the tool's definition Tool name is 'delete_snippet' and description states 'Delete a snippet from the phone' — this is irreversible deletion of user data.

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

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

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

delete_snippet 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 PhonePi MCP — 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 delete_snippet tool do? +

Delete a snippet from the phone. It is categorised as a Destructive tool in the PhonePi MCP 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_snippet? +

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

What risk level is delete_snippet? +

delete_snippet 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_snippet? +

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

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

delete_snippet is provided by the PhonePi MCP server (priyankark/phonepi-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every PhonePi MCP tool call.

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

Free to start. No card required.

22 PhonePi MCP 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.