Plan a Swiss public transport connection between two stations or addresses. Specify either when to depart (mode=
AI agents call plan_transit to retrieve information from Bergauf without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves public transport connection information (schedules, routes) between locations. It is a read/query operation with no side effects - it does not book tickets, make payments, or modify any data. It purely fetches transit planning information.
From the tool's definition Plan a Swiss public transport connection between two stations or addresses
Documented attack patterns abuse exactly the kind of access plan_transit gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Bergauf, and nothing reaches the server without passing your rules. This is the rule we recommend for plan_transit:
{
"version": "1",
"default": "deny",
"tools": {
"plan_transit": {}
}
}plan_transit 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.
Plan a Swiss public transport connection between two stations or addresses. Specify either when to depart (mode=. It is categorised as a Read tool in the Bergauf MCP Server, which means it retrieves data without modifying state.
Register the Bergauf MCP server in PolicyLayer and add a rule for plan_transit: 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 Bergauf. Nothing to install.
plan_transit 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 plan_transit 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 plan_transit. 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.
plan_transit is provided by the Bergauf MCP server (lailo/bergauf). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Bergauf, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
7 Bergauf tools catalogued and risk-classified — across an index of 43,000+ MCP servers.