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

browser_storage_remove

Remove a key from localStorage or sessionStorage.

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

Questions about browser_storage_remove

What does the browser_storage_remove tool do? +

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.

How do I enforce a policy on browser_storage_remove? +

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.

What risk level is browser_storage_remove? +

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.

Can I rate-limit browser_storage_remove? +

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.

How do I block browser_storage_remove completely? +

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.

What MCP server provides browser_storage_remove? +

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.

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