Returns static map context for a stop: its marker and polylines for every route that serves it. No live data is fetched. Use this when you need to enrich an existing map with route shapes (e.g. overlay polylines alongside a get_stop_realtime map block) or when the user asks to visualise which rou...
AI agents call get_stop_geometry 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 |
|---|---|---|---|
stop_id | object | — | Municipal stop code shown on stop signage (e.g. 707). Accepts a positive integer or an equivalent digit-only string. |
Parameters from the server's own tool schema.
Even though get_stop_geometry 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.
Risk signalsBulk/mass operation — affects multiple targets
Documented attack patterns abuse exactly the kind of access get_stop_geometry 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_stop_geometry:
{
"version": "1",
"default": "deny",
"tools": {
"get_stop_geometry": {}
}
}get_stop_geometry 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.
Returns static map context for a stop: its marker and polylines for every route that serves it. No live data is fetched. Use this when you need to enrich an existing map with route shapes (e.g. overlay polylines alongside a get_stop_realtime map block) or when the user asks to visualise which routes pass a stop without needing live arrivals. Do NOT use this when live arrival times or vehicle positions are needed — use get_stop_realtime instead. Requires a numeric stop ID; call get_stops_around_location first if you only have coordinates. It is categorised as a Read tool in the Lad Lviv Ua MCP Server, which means it retrieves data without modifying state.
get_stop_geometry accepts 1 parameter: stop_id. 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_stop_geometry: 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_stop_geometry 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_stop_geometry 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_stop_geometry. 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_stop_geometry 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.