Plan a public-transit (bus + metro) route between two points. Returns alternative plans sorted by recommendation, each broken into walking and ride segments. Coordinate system: this tool expects GCJ-02. The easiest source is bus_search.pois[*].lat/lng — those are already GCJ-02 and carry a name. ...
AI agents call bus_plan_transit to retrieve information from Chelaile without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries a transit routing service and returns route plans. It has no side effects, does not modify any data, and only retrieves/calculates transit route information between two points.
From the tool's definition Plan a public-transit (bus + metro) route between two points. Returns alternative plans sorted by recommendation
Documented attack patterns abuse exactly the kind of access bus_plan_transit gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Chelaile, and nothing reaches the server without passing your rules. This is the rule we recommend for bus_plan_transit:
{
"version": "1",
"default": "deny",
"tools": {
"bus_plan_transit": {}
}
}bus_plan_transit 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.
Plan a public-transit (bus + metro) route between two points. Returns alternative plans sorted by recommendation, each broken into walking and ride segments. Coordinate system: this tool expects GCJ-02. The easiest source is bus_search.pois[*].lat/lng — those are already GCJ-02 and carry a name. If you only have WGS-84 (e.g. from a phone GPS), convert it before calling. Args: - city_id (string, required) - origin_name, origin_lat, origin_lng (string, required): origin in GCJ-02 - dest_name, dest_lat, dest_lng (string, required): destination in GCJ-02 - strategy (. It is categorised as a Read tool in the Chelaile MCP Server, which means it retrieves data without modifying state.
Register the Chelaile MCP server in PolicyLayer and add a rule for bus_plan_transit: 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 Chelaile. Nothing to install.
bus_plan_transit 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 bus_plan_transit 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 bus_plan_transit. 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.
bus_plan_transit is provided by the Chelaile MCP server (peanutsplash/chelaile-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Chelaile, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
15 Chelaile tools catalogued and risk-classified — across an index of 43,000+ MCP servers.