Find public transport stations (train/bus/tram) near a WGS84 point. Useful for finding a trailhead station or the nearest stop to a finish point.
AI agents call nearest_stations 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 geospatial data about public transport stations near a given coordinate. It has no side effects, does not modify data, execute code, delete resources, or involve financial transactions. It is purely informational and supports the hiking planning use case by helping users locate transit access points.
From the tool's definition Tool name 'nearest_stations' and description 'Find public transport stations' indicates a query/lookup operation. Returns location data about transport infrastructure with no modification, creation, or execution of commands.
Documented attack patterns abuse exactly the kind of access nearest_stations 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 nearest_stations:
{
"version": "1",
"default": "deny",
"tools": {
"nearest_stations": {}
}
}nearest_stations 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.
Find public transport stations (train/bus/tram) near a WGS84 point. Useful for finding a trailhead station or the nearest stop to a finish point. 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 nearest_stations: 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.
nearest_stations 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 nearest_stations 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 nearest_stations. 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.
nearest_stations 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.