Get next arrivals at a specific stop.
AI agents call next_arrivals_tool to retrieve information from CATA Bus MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and returns arrival predictions for buses at a given stop. It performs a passive query against CATA's real-time bus data with no side effects, state changes, or external command execution. The potential for misuse is minimal — an agent cannot cause harm by requesting arrival times repeatedly or for multiple stops.
From the tool's definition Tool description states 'Get next arrivals at a specific stop' — a retrieval operation that queries real-time bus arrival data without modifying, deleting, or executing external operations.
Attacks that exploit this kind of access
Get next arrivals at a specific stop. It is categorised as a Read tool in the CATA Bus MCP Server MCP Server, which means it retrieves data without modifying state.
Register the CATA Bus MCP Server MCP server in PolicyLayer and add a rule for next_arrivals_tool: 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 CATA Bus MCP Server. Nothing to install.
next_arrivals_tool 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 next_arrivals_tool 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 next_arrivals_tool. 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.
next_arrivals_tool is provided by the CATA Bus MCP Server MCP server (pranav-karra-3301/catabus-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →