find_nearby_bus_stops
AI agents call find_nearby_bus_stops to retrieve information from UK Bus Departures 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 or queries bus stop location data based on proximity criteria—a classic Read category operation. No side effects, data modification, code execution, or destructive actions are implied. The empty description lowers confidence slightly, but the tool name and server context clearly indicate a search/retrieval function with minimal risk if misused by an AI agent.
From the tool's definition Tool name 'find_nearby_bus_stops' indicates a search/query operation that retrieves location-based bus stop data.
Attacks that exploit this kind of access
find_nearby_bus_stops. It is categorised as a Read tool in the UK Bus Departures MCP Server MCP Server, which means it retrieves data without modifying state.
Register the UK Bus Departures MCP Server MCP server in PolicyLayer and add a rule for find_nearby_bus_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 UK Bus Departures MCP Server. Nothing to install.
find_nearby_bus_stops 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 find_nearby_bus_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.
Set action: deny in the PolicyLayer policy for find_nearby_bus_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.
find_nearby_bus_stops is provided by the UK Bus Departures MCP Server MCP server (vandamd/bustimes-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 →