browser_storage_remove
Remove a key from localStorage or sessionStorage.
This record as markdown: /tools/salviz-termux-browser-pilot/browser-storage-remove.md
What browser_storage_remove does on Termux Browser Pilot
AI agents call browser_storage_remove 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_storage_remove is rated Critical
This tool irreversibly deletes a specific key from browser storage (localStorage or sessionStorage). While scoped to browser storage rather than files or databases, removal of storage keys can destroy session state, authentication tokens, or application data that may be difficult or impossible to recover, making it Destructive rather than merely Write.
From the tool's definition Remove a key from localStorage or sessionStorage
Attacks that exploit this kind of access
The rule that runs browser_storage_remove safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Termux Browser Pilot, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For browser_storage_remove, this is the rule to start with:
browser_storage_remove is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Termux Browser Pilot, apply this rule, and every browser_storage_remove call is checked against it from then on.
Questions about browser_storage_remove
Remove a key from localStorage or sessionStorage. 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_storage_remove: 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_storage_remove 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_storage_remove 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_storage_remove. 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_storage_remove 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.
Across the catalogue