Full detail for a stop: precise WGS-84 coordinates, every line that passes through (with first/last/price), realtime buses, and nearby metro lines. Args: - city_id (string, required) - physical_st_id (string, required): from bus_get_nearby_stops / bus_search - namesake_st_id (string, optional): r...
AI agents call bus_get_stop_detail 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 is a pure data retrieval tool that queries public transit information. It accepts stop identifiers and optional parameters to return detailed information about a transit stop, including location data, route information, and realtime bus arrivals. No data is created, modified, deleted, or executed—only queried.
From the tool's definition Tool retrieves 'full detail for a stop: precise WGS-84 coordinates, every line that passes through, realtime buses, and nearby metro lines.' All operations are query-based (get_stop_detail, list lines, retrieve coordinates, fetch realtime data) with no…
Risk signalsBulk/mass operation — affects multiple targets
Documented attack patterns abuse exactly the kind of access bus_get_stop_detail 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_get_stop_detail:
{
"version": "1",
"default": "deny",
"tools": {
"bus_get_stop_detail": {}
}
}bus_get_stop_detail 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.
Full detail for a stop: precise WGS-84 coordinates, every line that passes through (with first/last/price), realtime buses, and nearby metro lines. Args: - city_id (string, required) - physical_st_id (string, required): from bus_get_nearby_stops / bus_search - namesake_st_id (string, optional): recommended; from the same source - first_line_id (string, optional): a line to highlight - lat / lng (string, optional): caller. 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_get_stop_detail: 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_get_stop_detail 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_get_stop_detail 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_get_stop_detail. 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_get_stop_detail 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.