run_simple_simulation

THE RISK

High Risk

This tool executes an external simulation system with effects that vary based on provided parameters. While not destructive to persistent data, it can consume compute resources, generate outputs, and produce side effects in the simulation environment. This places it in the Execute category rather than Read (which would be query-only) or Write (which would be reversible data modification).

From the tool's definition The tool 'run_simple_simulation' executes a SUMO simulation using a config file. SUMO (Simulation of Urban Mobility) is an external simulation engine.

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

HOW TO CONTROL RUN_SIMPLE_SIMULATION

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

policy.json

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

run_simple_simulation 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 SUMO-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

More SUMO-MCP Server tools

Execute control_simulation Control SUMO simulation (connect, step, disconnect). Execute manage_demand Manage traffic demand (random trips, OD matrix, routing). Execute manage_rl_task Manage RL tasks (list scenarios, custom training). Execute optimize_traffic_signals Optimize traffic signals. Write convert_ezdesignx_network Convert an ezdesignX v1 JSON or JSONC intersection file into SUMO network artifacts. Write manage_network Manage SUMO network (generate, convert, or download OSM). Read run_analysis Analyze FCD output. Read get_sumo_info Get the version and path of the installed SUMO.

All 10 SUMO-MCP Server tools →

Execute tools on other servers

Frida Game Hacking MCP remove_breakpoint Procmon request_elevation WireMCP capture_packets Pentest Ai run_probe

Go deeper

High-risk tools in SUMO-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.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

What does the run_simple_simulation tool do? +

Run a SUMO simulation using a config file. It is categorised as a Execute tool in the SUMO-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 run_simple_simulation? +

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

What risk level is run_simple_simulation? +

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

Can I rate-limit run_simple_simulation? +

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

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

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

Enforce policy on every SUMO-MCP Server tool call.

Deterministic rules across all 10 SUMO-MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

GOVERN SUMO-MCP →

Free to start. No card required.

10 SUMO-MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.

// WHAT RUN_SIMPLE_SIMULATION ON SUMO-MCP SERVER DOES

// THE RISK

// HOW TO CONTROL RUN_SIMPLE_SIMULATION

// EXPLORE