transport-rest.transit.nearby_stops
Find public transit stops/stations near a latitude/longitude coordinate in Berlin/Brandenburg, sorted by walking distance. Useful for "what transit is near this address" queries. Data: v6.bvg.transport.rest (community HAFAS wrapper for BVG), no auth required, 100 req/min.
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/transport-rest.transit.nearby-stops.md
What transport-rest.transit.nearby_stops does on Apibase
AI agents call transport-rest.transit.nearby_stops to retrieve information from Apibase without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
results | integer | — | Maximum number of nearby stops to return (default 8, max 50). |
latitude | number | Yes | Latitude of the search point (WGS84). |
longitude | number | Yes | Longitude of the search point (WGS84). |
max_distance_meters | integer | — | Maximum walking distance in meters from the search point. Omit for no limit. |
Parameters from the server's own tool schema.
Why transport-rest.transit.nearby_stops is rated Low
Tool retrieves transit stop data without modifying or executing anything; purely informational query.
From the tool's definition Find public transit stops near latitude/longitude coordinate, sorted by distance.
Attacks that exploit this kind of access
The rule that runs transport-rest.transit.nearby_stops safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Apibase, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For transport-rest.transit.nearby_stops, this is the rule to start with:
transport-rest.transit.nearby_stops is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Apibase, apply this rule, and every transport-rest.transit.nearby_stops call is checked against it from then on.
Questions about transport-rest.transit.nearby_stops
Find public transit stops/stations near a latitude/longitude coordinate in Berlin/Brandenburg, sorted by walking distance. Useful for "what transit is near this address" queries. Data: v6.bvg.transport.rest (community HAFAS wrapper for BVG), no auth required, 100 req/min. It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
transport-rest.transit.nearby_stops accepts 4 parameters: results, latitude, longitude, max_distance_meters. Required: latitude, longitude. The full parameter table on this page comes from the server's own tool schema.
Register the Apibase MCP server in PolicyLayer and add a rule for transport-rest.transit.nearby_stops: 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 Apibase. Nothing to install.
transport-rest.transit.nearby_stops 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 transport-rest.transit.nearby_stops 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 transport-rest.transit.nearby_stops. 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.
transport-rest.transit.nearby_stops is provided by the Apibase MCP server (apibase-mcp-client). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Apibase, and thousands of servers like it.
This server
Across the catalogue