Plans a transit trip from an origin stop to a destination stop using the static route graph. Returns direct options (single route) and 1-transfer options sorted by fewest stops. Use when the user asks 'how do I get from A to B?' or needs route recommendations between two stops. Requires numeric s...
Part of the Lviv Public Transport server.
Free to start. No card required.
AI agents use plan_trip to create or modify resources in Lviv Public Transport. Write operations carry medium risk because an autonomous agent could trigger bulk unintended modifications. Rate limits prevent a single agent session from making hundreds of changes in rapid succession. Argument validation ensures the agent passes expected values.
Without a policy, an AI agent could call plan_trip repeatedly, creating or modifying resources faster than any human could review. PolicyLayer's rate limiting ensures write operations happen at a controlled pace, and argument validation catches malformed or unexpected inputs before they reach Lviv Public Transport.
Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.
{
"version": "1",
"default": "deny",
"tools": {
"plan_trip": {
"limits": [
{
"counter": "plan_trip_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}See the full Lviv Public Transport policy for all 8 tools.
These attack patterns abuse exactly the kind of access plan_trip gives an agent. Each links to the full case and the policy that stops it:
Other write tools across the catalogue. The same approach applies to each: rate-limit and validate the arguments.
Plans a transit trip from an origin stop to a destination stop using the static route graph. Returns direct options (single route) and 1-transfer options sorted by fewest stops. Use when the user asks 'how do I get from A to B?' or needs route recommendations between two stops. Requires numeric stop codes for both origin and destination; use get_stops_around_location first if you only have addresses or coordinates. Does NOT account for realtime service disruptions or live vehicle positions — combine with get_stop_realtime for live ETAs after planning.. It is categorised as a Write tool in the Lviv Public Transport MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Lviv Public Transport MCP server in PolicyLayer and add a rule for plan_trip: 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 Lviv Public Transport. Nothing to install.
plan_trip is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the plan_trip 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 plan_trip. 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.
plan_trip is provided by the Lviv Public Transport MCP server (https://api.lad.lviv.ua/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 8 Lviv Public Transport tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
4,600+ MCP servers and 31,000+ tools scanned and risk-classified.