Search incidents by line, title, or description
AI agents call search_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 performs a search/query operation on cached MVG disruption data. It retrieves information about public transport incidents based on user-provided search criteria (line, title, or description). There are no side effects, no data modification, no code execution, and no financial implications. This is a straightforward Read operation with minimal risk.
From the tool's definition Tool name 'search_incidents' combined with description 'Search incidents by line, title, or description' indicates a query operation that retrieves and filters existing disruption data without modifying, deleting, or executing any operations.
Attacks that exploit this kind of access
Search incidents by line, title, or description. 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 search_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.
search_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 search_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 search_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.
search_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 →