test_scenario_status

A read tool on the Looking Glass MCP server.

SERVERLooking Glass SOURCElooking-glass-mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee 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-scenario-status.md

WHAT IT DOES

What test_scenario_status does on Looking Glass

AI agents call test_scenario_status to retrieve information from Looking Glass without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why test_scenario_status is rated Low

The naming convention ('status' suffix) and context within a browser automation server suggests this tool retrieves status information about test scenarios. Without side effects evident from the name and no description to contradict this interpretation, it falls into the Read category (queries/retrieves data). Severity is low as status checks have minimal blast radius.

From the tool's definition Tool name 'test_scenario_status' suggests querying the status of test scenarios, which implies data retrieval without side effects. The description is empty, limiting certainty.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

test_scenario_status Allowed

test_scenario_status is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "test_scenario_status": {}
  }
}

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

FAQ

Questions about test_scenario_status

What does the test_scenario_status tool do? +

test_scenario_status is a read tool on the Looking Glass MCP server. It is categorised as a Read tool in the Looking Glass MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on test_scenario_status? +

Register the Looking Glass MCP server in PolicyLayer and add a rule for test_scenario_status: 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_scenario_status? +

test_scenario_status is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit test_scenario_status? +

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

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

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

Across the catalogue

claude_git_status on Claude Bridge →get_task_status on 0rca Dojo MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →