AI agents call browser_session_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.
The tool permanently removes a saved browser session, which cannot be undone. This is a destructive action rather than merely a Write operation because deletion is irreversible. The severity is high because malicious use could erase user browsing history, authentication states, or other session data that the user may depend on, though the blast radius is limited to a single session rather than broader system impact.
From the tool's definition Tool name contains 'delete' and description states 'Delete a saved session' - this is an irreversible destruction of user data (session state/history).
Documented attack patterns abuse exactly the kind of access browser_session_delete gives an agent:
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_session_delete:
{
"version": "1",
"default": "deny",
"hide": [
"browser_session_delete"
]
}browser_session_delete disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.
Free to start. No card required.
Delete a saved session. 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.
Register the Termux Browser Pilot MCP server in PolicyLayer and add a rule for browser_session_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.
browser_session_delete is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the browser_session_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.
Set action: deny in the PolicyLayer policy for browser_session_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.
browser_session_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.
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.