Manage traffic demand (random trips, OD matrix, routing).
AI agents invoke manage_demand to trigger actions in SUMO-MCP Server. 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.
This tool generates and manages traffic demand inputs — creating random trips, processing OD matrices, and computing routes — which triggers external computation and file generation within the SUMO simulation environment. It goes beyond a simple read/write of data as it executes demand modeling processes (trip generation, routing algorithms).
From the tool's definition Manage traffic demand (random trips, OD matrix, routing)
Documented attack patterns abuse exactly the kind of access manage_demand 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 manage_demand:
{
"version": "1",
"default": "deny",
"tools": {
"manage_demand": {
"limits": [
{
"counter": "manage_demand_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}manage_demand 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.
Free to start. No card required.
Manage traffic demand (random trips, OD matrix, routing). 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.
Register the SUMO-MCP Server MCP server in PolicyLayer and add a rule for manage_demand: 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.
manage_demand 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 manage_demand 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 manage_demand. 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.
manage_demand 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.
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.