AI agents call get_sumo_info 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.
This tool retrieves metadata about the SUMO installation (version and path information) without creating, modifying, deleting, or executing any operations. It is a simple read/query operation with no side effects on the traffic simulation or underlying systems.
From the tool's definition Tool name is 'get_sumo_info' and description states 'Get the version and path of the installed SUMO' — purely informational retrieval with no modification or execution of simulation systems.
Documented attack patterns abuse exactly the kind of access get_sumo_info 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 get_sumo_info:
{
"version": "1",
"default": "deny",
"tools": {
"get_sumo_info": {}
}
}get_sumo_info is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get the version and path of the installed SUMO. It is categorised as a Read tool in the SUMO-MCP Server MCP Server, which means it retrieves data without modifying state.
Register the SUMO-MCP Server MCP server in PolicyLayer and add a rule for get_sumo_info: 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.
get_sumo_info is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_sumo_info 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 get_sumo_info. 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.
get_sumo_info 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.