Critical Risk →

browser_profile_delete

Delete a saved browser profile.

How to control browser_profile_delete ↓

What browser_profile_delete does on Termux Browser Pilot

AI agents call browser_profile_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.

Critical Risk

Why browser_profile_delete needs a policy

Deleting a browser profile is an irreversible action that destroys saved settings, cookies, history, passwords, and other persistent user data. This falls into the Destructive category (not merely Write) because the effect cannot be undone. The severity is high because an agent misusing this tool could permanently erase critical authentication credentials or user configurations.

From the tool's definition Tool name explicitly contains 'delete' and description states 'Delete a saved browser profile' — irreversible removal of stored data.

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

How to control browser_profile_delete

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

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

browser_profile_delete 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 Termux Browser Pilot — 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 browser_profile_delete

What does the browser_profile_delete tool do? +

Delete a saved browser profile. 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_profile_delete? +

Register the Termux Browser Pilot MCP server in PolicyLayer and add a rule for browser_profile_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_profile_delete? +

browser_profile_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_profile_delete? +

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

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

browser_profile_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.

Enforce policy on every Termux Browser Pilot tool call.

Start from Termux Browser Pilot, 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.

148 Termux Browser Pilot 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.