Returns static route metadata: short and long name, vehicle type, brand colour, ordered stop lists for both directions, and route polylines (shapes) for map rendering. Use when the user asks which stops a route serves, what a route looks like on a map, or what the scheduled departure times are. D...
AI agents call get_route_static 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 |
|---|---|---|---|
route_name | string | — | Route short name (e.g. "T30", "32A") or numeric external ID. |
Parameters from the server's own tool schema.
Even though get_route_static 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_route_static 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_route_static:
{
"version": "1",
"default": "deny",
"tools": {
"get_route_static": {}
}
}get_route_static 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 route metadata: short and long name, vehicle type, brand colour, ordered stop lists for both directions, and route polylines (shapes) for map rendering. Use when the user asks which stops a route serves, what a route looks like on a map, or what the scheduled departure times are. Do NOT use this when live vehicle positions are needed — use get_route_realtime instead. Requires a route short name (e.g. "T30", "32A") or numeric external ID; call get_stops_around_location first if you only know a location and need to discover which routes serve it. It is categorised as a Read tool in the Lad Lviv Ua MCP Server, which means it retrieves data without modifying state.
get_route_static accepts 1 parameter: route_name. 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_route_static: 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_route_static 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_route_static 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_route_static. 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_route_static 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.