Low Risk

query_simulation_state

Query simulation state (vehicles, speed, position). Requires active connection.

How to control query_simulation_state ↓

AI agents call query_simulation_state to retrieve information from SUMO-MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

This tool reads and queries the current state of a traffic simulation (vehicle positions, speeds, etc.) without side effects. It requires an active connection but performs no destructive, write, execute, or financial operations.

From the tool's definition Tool description states it 'Query[ies] simulation state (vehicles, speed, position)' - purely retrieval of data with no modification, deletion, or execution capability.

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

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 query_simulation_state:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "query_simulation_state": {}
  }
}

query_simulation_state is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register SUMO-MCP Server — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Go deeper

What does the query_simulation_state tool do? +

Query simulation state (vehicles, speed, position). Requires active connection. It is categorised as a Read tool in the SUMO-MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on query_simulation_state? +

Register the SUMO-MCP Server MCP server in PolicyLayer and add a rule for query_simulation_state: 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 query_simulation_state? +

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

Can I rate-limit query_simulation_state? +

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

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

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

Free to start. No card required.

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

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.