test_scenario_run
A execute tool on the Looking Glass MCP server.
This record as markdown: /tools/io-github-sahib-sawhney-wh-looking-glass-mcp/test-scenario-run.md
What test_scenario_run does on Looking Glass
AI agents invoke test_scenario_run 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 |
|---|---|---|---|
name | string | Yes | Scenario name |
steps | array | Yes | Array of test steps to execute. Steps can use {{variable}} placeholders when dataSets is provided. |
baseUrl | string | — | Base URL (e.g., http://localhost:3000) |
dataSets | array | — | Data sets for parameterized testing. The scenario runs once per data set with {{variable}} substitution. |
Parameters from the server's own tool schema.
Why test_scenario_run is rated High
The name suggests execution of a scenario (likely browser automation or scripted test steps), which falls under Execute. The server context is an AI-native browser for agents with self-healing capabilities, making arbitrary scenario execution potentially high-impact. Confidence is reduced due to the empty description.
From the tool's definition Tool name 'test_scenario_run' implies running/executing a test scenario; description is empty and uninformative.
Risk signalsAccepts freeform code/query input (steps[].query) · Accepts URL/endpoint input (steps[].url) · Handles credentials or secrets (steps[].password) · High parameter count (24 properties)
Attacks that exploit this kind of access
The rule that runs test_scenario_run 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_scenario_run, this is the rule to start with:
test_scenario_run 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_scenario_run call is checked against it from then on.
Questions about test_scenario_run
test_scenario_run 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_scenario_run accepts 4 parameters: name, steps, baseUrl, dataSets. Required: name, steps. 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_scenario_run: 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_scenario_run 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_scenario_run 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_scenario_run. 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_scenario_run 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