Get information about the cache status
AI agents call get_cache_status 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 retrieves cache status information, which is a read-only operation with no side effects. It queries internal state about data caching for the MVG disruption service. The blast radius of misuse is minimal—an agent could at worst spam requests or learn internal cache implementation details, but cannot modify data, execute commands, or cause financial harm.
From the tool's definition Tool name 'get_cache_status' and description 'Get information about the cache status' indicate a query operation that retrieves cache metadata without modifying data or triggering external operations.
Attacks that exploit this kind of access
Get information about the cache status. 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_cache_status: 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_cache_status 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_cache_status 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_cache_status. 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_cache_status 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 →