switch_scenario

THE RISK

High Risk

Why switch_scenario needs a policy

This tool triggers an operational state change on a running mock server by switching which scenario is active. It affects server behavior for subsequent requests, constituting an external operation rather than a simple read or write. It's not destructive (reversible by switching back), not financial, but does execute a behavioral change on a live server component.

From the tool's definition Switches active scenario on a server

Documented attack patterns abuse exactly the kind of access switch_scenario gives an agent:

POLICY

How to control switch_scenario

PolicyLayer is an MCP gateway — it sits between your AI agents and MockLoop MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for switch_scenario:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "switch_scenario": {
      "limits": [
        {
          "counter": "switch_scenario_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

switch_scenario 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.

Create a free account and register MockLoop MCP Server — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

RATE-LIMIT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More MockLoop MCP Server tools

Execute deploy_scenario Deploys scenario to MockLoop server. Execute execute_test_plan Combines scenario generation and deployment in one operation. Execute run_load_test Executes load testing with configurable parameters. Execute run_security_test Executes security testing scenarios for vulnerability assessment. Execute run_test_iteration Executes a single test iteration with monitoring. Execute generate_mock_api Generates a FastAPI mock server from an API specification (e.g., OpenAPI). Execute schedule_test_suite Schedules automated test suite execution. Write end_test_session Ends a test session and generates final reports.

All 30 MockLoop MCP Server tools →

Execute tools on other servers

Android Forensics ADB MCP Server adb_shell_command EMBA-MCP run_emba_scan Frida Game Hacking MCP remove_breakpoint Procmon request_elevation

Go deeper

High-risk tools in MockLoop MCP Server → Every high-risk tool this server exposes, in one view.
All high-risk MCP tools → Every high-risk tool across the catalogue, and the policy pattern that contains them.
The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Agent sandbox → Bounding what an agent can execute and where the boundary should sit.
Least privilege for MCP → Granting agents the minimum tool surface the task needs.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about switch_scenario

What does the switch_scenario tool do? +

Switches active scenario on a server. It is categorised as a Execute tool in the MockLoop MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on switch_scenario? +

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

What risk level is switch_scenario? +

switch_scenario is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit switch_scenario? +

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

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

switch_scenario is provided by the MockLoop MCP Server MCP server (mockloop/mockloop-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every MockLoop MCP Server tool call.

Start from MockLoop MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →