Get all London bus routes, optionally filtered by route number or name.
AI agents call get_bus_routes to retrieve information from TFL MCP Server for Poke without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and retrieves publicly available London bus route information. It has no side effects, cannot modify or delete data, and does not execute code or trigger external operations. It is consistent with other sibling tools (get_arrivals, get_line_status) that are all read operations against a public transit API.
From the tool's definition Tool name 'get_bus_routes' with description 'Get all London bus routes, optionally filtered by route number or name' indicates data retrieval with no modification, deletion, or execution capabilities.
Attacks that exploit this kind of access
Get all London bus routes, optionally filtered by route number or name. It is categorised as a Read tool in the TFL MCP Server for Poke MCP Server, which means it retrieves data without modifying state.
Register the TFL MCP Server for Poke MCP server in PolicyLayer and add a rule for get_bus_routes: 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 TFL MCP Server for Poke. Nothing to install.
get_bus_routes 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 get_bus_routes 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 get_bus_routes. 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.
get_bus_routes is provided by the TFL MCP Server for Poke MCP server (vjagiasi/tfl-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 →