New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

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), ...

SERVERApibase SOURCEapibase-mcp-client
Low RISK CLASS
Category Read
Parameters 41 required
Recommended Allowedsee the rule below
Registry record Grade F, identity unverified Pull the record →

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.

ParameterTypeRequiredDescription
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.

Questions about transport-rest.transit.search_locations

What does the transport-rest.transit.search_locations tool do? +

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.

What parameters does transport-rest.transit.search_locations accept? +

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.

How do I enforce a policy on transport-rest.transit.search_locations? +

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.

What risk level is transport-rest.transit.search_locations? +

transport-rest.transit.search_locations is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit transport-rest.transit.search_locations? +

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.

How do I block transport-rest.transit.search_locations completely? +

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.

What MCP server provides transport-rest.transit.search_locations? +

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.

Across the catalogue

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Apibase's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.