Get current MVG incidents (cached for 10+ minutes)
AI agents call get_mvg_incidents to retrieve information from MVG Störung MCP Server (inofficial) without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool only queries and retrieves public transportation disruption data. It has no side effects, cannot modify any data, and presents no financial risk. The 10+ minute cache indicates it is a read-only information retrieval mechanism. The low severity reflects minimal impact even if an AI agent misuses it by making excessive queries.
From the tool's definition Tool retrieves current MVG incidents from cached data with no capability to modify, delete, or execute operations. The description states it is a GET operation returning cached disruption information.
Attacks that exploit this kind of access
Get current MVG incidents (cached for 10+ minutes). It is categorised as a Read tool in the MVG Störung MCP Server (inofficial) MCP Server, which means it retrieves data without modifying state.
Register the MVG Störung MCP Server (inofficial) MCP server in PolicyLayer and add a rule for get_mvg_incidents: 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 MVG Störung MCP Server (inofficial). Nothing to install.
get_mvg_incidents 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_mvg_incidents 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_mvg_incidents. 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_mvg_incidents is provided by the MVG Störung MCP Server (inofficial) MCP server (rmoriz/mvg_stoerung_mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →