transport-rest.transit.search_locations
Search for public transit stops/stations, addresses, or points of interest in Berlin/Brandenburg by name (e.g. "Alexanderplatz"). Returns location IDs and coordinates to use with departures, journey planning, and nearby-stop lookups. Data: v6.bvg.transport.rest (community HAFAS wrapper for BVG), ...
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/transport-rest.transit.search-locations.md
What transport-rest.transit.search_locations does on Apibase
AI agents call transport-rest.transit.search_locations 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 |
|---|---|---|---|
query | string | Yes | Search text for a stop/station, address, or point of interest (e.g. "Alexanderplatz" or "Unter den Linden 1, Berlin"). Returns matching location IDs to use in o |
results | integer | — | Maximum number of matching locations to return (default 10, max 50). |
include_poi | boolean | — | Include points of interest (landmarks, venues) in results, not just stops. Default false. |
include_addresses | boolean | — | Include street addresses in results, not just stops. Default false. |
Parameters from the server's own tool schema.
Why transport-rest.transit.search_locations is rated Low
Tool queries transit location data without modifying state or executing external operations.
From the tool's definition Search for public transit stops/stations, addresses, or points of interest. Returns location IDs and coordinates.
Attacks that exploit this kind of access
The rule that runs transport-rest.transit.search_locations 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.search_locations, this is the rule to start with:
transport-rest.transit.search_locations 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.search_locations call is checked against it from then on.
Questions about transport-rest.transit.search_locations
Search for public transit stops/stations, addresses, or points of interest in Berlin/Brandenburg by name (e.g. "Alexanderplatz"). Returns location IDs and coordinates to use with departures, journey planning, and nearby-stop lookups. 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.search_locations accepts 4 parameters: query, results, include_poi, include_addresses. Required: query. 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.search_locations: 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.search_locations 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.search_locations 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.search_locations. 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.search_locations 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