browser_mock_clear

Remove response mock(s).

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-mock-clear.md

WHAT IT DOES

What browser_mock_clear does on Termux Browser Pilot

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

RISK

Why browser_mock_clear is rated Critical

This tool irreversibly removes/deletes browser response mocks. Deletion of mocks cannot be undone and falls under the Destructive category. Severity is medium since the blast radius is limited to browser mock configurations rather than persistent user data.

From the tool's definition Remove response mock(s)

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs browser_mock_clear 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_mock_clear, this is the rule to start with:

browser_mock_clear Hidden

browser_mock_clear is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "browser_mock_clear"
  ]
}

RESTRICT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Termux Browser Pilot, apply this rule, and every browser_mock_clear call is checked against it from then on.

FAQ

Questions about browser_mock_clear

What does the browser_mock_clear tool do? +

Remove response mock(s). 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_mock_clear? +

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

browser_mock_clear 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_mock_clear? +

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

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

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

KEEP EXPLORING

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

This server

All 148 Termux Browser Pilot tools → Critical-risk tools on this server →

Across the catalogue

clear_renders on Why Did You Render →knowledge_clear on Templonix Lite MCP Server →clear_scan on Frida Game Hacking MCP →clear_spam_box on cPanel MCP Server → All critical-risk MCP tools → The MCP Attack Database →

Guides

Govern database agents →Blast radius →Tool call approval →