test_chaos
A execute tool on the Looking Glass MCP server.
This record as markdown: /tools/io-github-sahib-sawhney-wh-looking-glass-mcp/test-chaos.md
What test_chaos does on Looking Glass
AI agents invoke test_chaos to trigger actions in Looking Glass. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
| Parameter | Type | Required | Description |
|---|---|---|---|
delayMs | number | — | Max delay for random-delays profile (default: 2000ms) |
profile | string | Yes | Chaos condition to apply |
urlPattern | string | — | URL pattern for block-api profile (default: /api/) |
Parameters from the server's own tool schema.
Why test_chaos is rated High
The name 'test_chaos' implies running some form of chaos engineering or disruptive testing, which would fall under Execute or potentially Destructive. However, with no description available, confidence is low. Given the context of a browser automation server with tools like browser_clean_slate and browser_clear_storage, this could trigger destructive browser state operations.
From the tool's definition Tool name 'test_chaos' suggests execution of chaos/stress testing operations, but description is empty and uninformative.
Attacks that exploit this kind of access
The rule that runs test_chaos 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, this is the rule to start with:
test_chaos stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Looking Glass, apply this rule, and every test_chaos call is checked against it from then on.
Questions about test_chaos
test_chaos is a execute tool on the Looking Glass MCP server. It is categorised as a Execute tool in the Looking Glass MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
test_chaos accepts 3 parameters: delayMs, profile, urlPattern. Required: profile. The full parameter table on this page comes from the server's own tool schema.
Register the Looking Glass MCP server in PolicyLayer and add a rule for test_chaos: 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.
test_chaos is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the test_chaos 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 test_chaos. 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.
test_chaos 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.
More on Looking Glass, and thousands of servers like it.
Across the catalogue