Low Risk

bus_refresh_lines

Refresh realtime bus info for several (line, stop) pairs in one round-trip. Useful for a

How to control bus_refresh_lines ↓

What bus_refresh_lines does on Chelaile

AI agents call bus_refresh_lines 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_refresh_lines needs a policy

This tool retrieves current realtime bus information for specified line and stop pairs. It has no side effects—it does not create, modify, delete, or execute commands. The 'refresh' operation is a read operation that fetches updated transit state. Misuse by an AI agent would only result in excessive queries or information disclosure, not data modification or destructive actions.

From the tool's definition Tool name 'bus_refresh_lines' and description 'Refresh realtime bus info for several (line, stop) pairs' indicates querying/refreshing current transit data.

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

How to control bus_refresh_lines

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

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

bus_refresh_lines 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_refresh_lines

What does the bus_refresh_lines tool do? +

Refresh realtime bus info for several (line, stop) pairs in one round-trip. Useful for a. 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_refresh_lines? +

Register the Chelaile MCP server in PolicyLayer and add a rule for bus_refresh_lines: 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_refresh_lines? +

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

Can I rate-limit bus_refresh_lines? +

Yes. Add a rate_limit block to the bus_refresh_lines 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_refresh_lines completely? +

Set action: deny in the PolicyLayer policy for bus_refresh_lines. 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_refresh_lines? +

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