Low Risk

bus_get_nearby_stops

List bus stops near a WGS-84 GPS coordinate, each annotated with the lines that pass through and the realtime buses approaching. If you don

How to control bus_get_nearby_stops ↓

What bus_get_nearby_stops does on Chelaile

AI agents call bus_get_nearby_stops 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.

Low Risk

Why bus_get_nearby_stops needs a policy

This tool retrieves and queries public transit data (nearby stops, route information, bus arrival times) with no side effects. It performs a geospatial search around a coordinate and returns annotated results. No data is created, modified, deleted, or executed. This is a classic Read operation with minimal security risk—the worst case is disclosure of public transit information, which is already publicly available.

From the tool's definition Tool name contains 'get' and 'list'; description states it 'List[s] bus stops' and retrieves 'realtime buses approaching' — purely informational queries with no modification, deletion, or execution of commands.

Documented attack patterns abuse exactly the kind of access bus_get_nearby_stops gives an agent:

How to control bus_get_nearby_stops

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_nearby_stops:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "bus_get_nearby_stops": {}
  }
}

bus_get_nearby_stops is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Chelaile — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about bus_get_nearby_stops

What does the bus_get_nearby_stops tool do? +

List bus stops near a WGS-84 GPS coordinate, each annotated with the lines that pass through and the realtime buses approaching. If you don. It is categorised as a Read tool in the Chelaile MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on bus_get_nearby_stops? +

Register the Chelaile MCP server in PolicyLayer and add a rule for bus_get_nearby_stops: 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.

What risk level is bus_get_nearby_stops? +

bus_get_nearby_stops is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit bus_get_nearby_stops? +

Yes. Add a rate_limit block to the bus_get_nearby_stops 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.

How do I block bus_get_nearby_stops completely? +

Set action: deny in the PolicyLayer policy for bus_get_nearby_stops. 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.

What MCP server provides bus_get_nearby_stops? +

bus_get_nearby_stops 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.

Enforce policy on every Chelaile tool call.

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.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.