Plan a journey between two locations using TFL. Returns route options with duration and step-by-step directions. Use specific station names like
AI agents call plan_journey 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 the TFL journey planning API and returns read-only route information (options, duration, directions). It has no side effects, does not modify any data, and cannot cause harm if misused — it simply retrieves travel planning data.
From the tool's definition Plan a journey between two locations using TFL. Returns route options with duration and step-by-step directions.
Attacks that exploit this kind of access
Plan a journey between two locations using TFL. Returns route options with duration and step-by-step directions. Use specific station names like. 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 plan_journey: 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.
plan_journey 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 plan_journey 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 plan_journey. 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.
plan_journey 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 →