get_passenger_frequency
AI agents call get_passenger_frequency to retrieve information from Swiss Rail without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves passenger frequency statistics, a read-only data query with no side effects. Even if this data were sensitive, querying it poses minimal risk compared to other categories. The zero-authentication design and sibling tools reinforce that this server is intended for safe information retrieval about public transport systems.
From the tool's definition Tool name 'get_passenger_frequency' and server context (Swiss public transport query service) indicate this retrieves passenger data.
Attacks that exploit this kind of access
get_passenger_frequency. It is categorised as a Read tool in the Swiss Rail MCP Server, which means it retrieves data without modifying state.
Register the Swiss Rail MCP server in PolicyLayer and add a rule for get_passenger_frequency: 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 Swiss Rail. Nothing to install.
get_passenger_frequency 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_passenger_frequency 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_passenger_frequency. 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_passenger_frequency is provided by the Swiss Rail MCP server (kintscher/swiss-rail-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 →