New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

browser_snapshot_delete

Delete a named snapshot.

SERVERTermux Browser Pilot SOURCEsalviz/termux-browser-pilot
Critical RISK CLASS
Category Destructive
Parameters 00 required
Recommended Hiddensee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/salviz-termux-browser-pilot/browser-snapshot-delete.md

What browser_snapshot_delete does on Termux Browser Pilot

AI agents call browser_snapshot_delete to permanently remove resources in Termux Browser Pilot, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Why browser_snapshot_delete is rated Critical

Deleting a snapshot is a destructive, non-reversible operation. Once a named snapshot is removed, it cannot be recovered. Severity is medium because the blast radius is limited to the loss of a saved browser state rather than system-wide data or financial consequences.

From the tool's definition "Delete a named snapshot" — the tool irreversibly removes a saved browser snapshot by name.

Questions about browser_snapshot_delete

What does the browser_snapshot_delete tool do? +

Delete a named snapshot. It is categorised as a Destructive tool in the Termux Browser Pilot 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 browser_snapshot_delete? +

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

What risk level is browser_snapshot_delete? +

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

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

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

browser_snapshot_delete is provided by the Termux Browser Pilot MCP server (salviz/termux-browser-pilot). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

More on Termux Browser Pilot, and thousands of servers like it.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Termux Browser Pilot's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.