browser_clear_mocks

A destructive tool on the Looking Glass MCP server.

SERVERLooking Glass SOURCElooking-glass-mcp

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/io-github-sahib-sawhney-wh-looking-glass-mcp/browser-clear-mocks.md

WHAT IT DOES

What browser_clear_mocks does on Looking Glass

AI agents call browser_clear_mocks to permanently remove resources in Looking Glass, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

RISK

Why browser_clear_mocks is rated Critical

The name 'browser_clear_mocks' suggests clearing/removing mock configurations or interceptors from the browser. Based on sibling tools (browser_clear_history, browser_clear_storage) which are destructive clearing operations, and the 'clear' verb in this tool's name, it likely irreversibly removes mock data or request interceptors.

From the tool's definition Tool name: browser_clear_mocks — description is empty and uninformative

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs browser_clear_mocks safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Looking Glass, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For browser_clear_mocks, this is the rule to start with:

browser_clear_mocks Hidden

browser_clear_mocks 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_clear_mocks"
  ]
}

RESTRICT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Looking Glass, apply this rule, and every browser_clear_mocks call is checked against it from then on.

FAQ

Questions about browser_clear_mocks

What does the browser_clear_mocks tool do? +

browser_clear_mocks is a destructive tool on the Looking Glass MCP server. It is categorised as a Destructive tool in the Looking Glass 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_clear_mocks? +

Register the Looking Glass MCP server in PolicyLayer and add a rule for browser_clear_mocks: 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 Looking Glass. Nothing to install.

What risk level is browser_clear_mocks? +

browser_clear_mocks 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_clear_mocks? +

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

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

browser_clear_mocks is provided by the Looking Glass MCP server (looking-glass-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Looking Glass, and thousands of servers like it.

This server

All 71 Looking Glass 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 code and CI agents →Blast radius →Tool call approval →