Get real-time arrival predictions at a TFL station or stop. Returns next trains/buses with times and destinations.
AI agents call get_arrivals 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 Transport for London's real-time systems to fetch and display arrival information. It is a read-only operation that retrieves current transit data without creating, modifying, or deleting any resources. No financial transactions, code execution, or destructive actions are involved.
From the tool's definition Tool returns 'real-time arrival predictions' with 'next trains/buses with times and destinations' — purely a data retrieval operation with no modification, deletion, or side effects.
Attacks that exploit this kind of access
Get real-time arrival predictions at a TFL station or stop. Returns next trains/buses with times and destinations. 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_arrivals: 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_arrivals 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_arrivals 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_arrivals. 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_arrivals 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 →