Manage SUMO network (generate, convert, or download OSM).
AI agents use manage_network to create or update resources in SUMO-MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your SUMO-MCP Server environment.
The tool performs Write operations by generating or converting network data structures in SUMO. While network generation affects simulation behavior, these changes are reversible (networks can be replaced or deleted separately). This is not Execute (doesn't run arbitrary code/commands based on user input in a way that's unpredictable), not Destructive (the operation itself is not irreversible), and not Financial.
From the tool's definition Tool description states it can 'generate, convert, or download OSM' networks. These are network creation and modification operations.
Documented attack patterns abuse exactly the kind of access manage_network 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_network:
{
"version": "1",
"default": "deny",
"tools": {
"manage_network": {
"limits": [
{
"counter": "manage_network_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}manage_network stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Manage SUMO network (generate, convert, or download OSM). It is categorised as a Write tool in the SUMO-MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the SUMO-MCP Server MCP server in PolicyLayer and add a rule for manage_network: 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_network is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the manage_network 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_network. 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_network 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.