Discovers transit stops near a geographic point, returning each stop's numeric code, name, coordinates, and walking distance. Also emits a map UI block with multiple markers for map-capable clients (e.g. ChatGPT). Use this as the first step whenever the user provides an address, place name, or co...
AI agents call get_stops_around_location to retrieve information from Lad Lviv Ua without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
latitude | number | — | Decimal latitude of the search centre, WGS84 (e.g. 49.842 for central Lviv). |
longitude | number | — | Decimal longitude of the search centre, WGS84 (e.g. 24.031 for central Lviv). |
radius_meters | integer | — | Search radius in metres (50–3000, default 1000). Use ~300 for dense urban intersections, up to 3000 for suburban or rural areas. |
Parameters from the server's own tool schema.
Even though get_stops_around_location only reads data, uncontrolled read access leaks sensitive information and racks up API costs — an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Documented attack patterns abuse exactly the kind of access get_stops_around_location gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Lad Lviv Ua, and nothing reaches the server without passing your rules. This is the rule we recommend for get_stops_around_location:
{
"version": "1",
"default": "deny",
"tools": {
"get_stops_around_location": {}
}
}get_stops_around_location 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.
Discovers transit stops near a geographic point, returning each stop's numeric code, name, coordinates, and walking distance. Also emits a map UI block with multiple markers for map-capable clients (e.g. ChatGPT). Use this as the first step whenever the user provides an address, place name, or coordinates and you need stop IDs before calling get_stop_realtime or get_stop_geometry. Do NOT use this to fetch arrivals or live vehicle data — it returns stop metadata only. Default radius is 1 000 m; narrow it (e.g. 300 m) for dense urban areas or widen it (up to 3 000 m) for rural locations. It is categorised as a Read tool in the Lad Lviv Ua MCP Server, which means it retrieves data without modifying state.
get_stops_around_location accepts 3 parameters: latitude, longitude, radius_meters. The full parameter table on this page comes from the server's own tool schema.
Register the Lad Lviv Ua MCP server in PolicyLayer and add a rule for get_stops_around_location: 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 Lad Lviv Ua. Nothing to install.
get_stops_around_location 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 get_stops_around_location 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 get_stops_around_location. 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.
get_stops_around_location is provided by the Lad Lviv Ua MCP server (vbhjckfd/lad-lviv-ua). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 5 Lad Lviv Ua tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
5 Lad Lviv Ua tools catalogued and risk-classified — across an index of 42,500+ MCP servers.