test_chaos_clear

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/test-chaos-clear.md

WHAT IT DOES

What test_chaos_clear does on Looking Glass

AI agents call test_chaos_clear 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 test_chaos_clear is rated Critical

The name combines 'chaos' (implying disruptive behavior) and 'clear' (implying deletion or wiping). Given the server context of browser automation with vault and storage tools, this likely clears or wipes some state irreversibly. Similar sibling tools like 'browser_clear_storage' and 'browser_clean_slate' are destructive in nature.

From the tool's definition Tool name 'test_chaos_clear' — 'clear' suggests irreversible removal; 'chaos' may imply disruptive/destructive test operations. Description is empty.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

test_chaos_clear Hidden

test_chaos_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": [
    "test_chaos_clear"
  ]
}

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 test_chaos_clear call is checked against it from then on.

FAQ

Questions about test_chaos_clear

What does the test_chaos_clear tool do? +

test_chaos_clear 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 test_chaos_clear? +

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

What risk level is test_chaos_clear? +

test_chaos_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 test_chaos_clear? +

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

Set action: deny in the PolicyLayer policy for test_chaos_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 test_chaos_clear? +

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