Get status for a specific London Underground line.
AI agents call get_line_status to retrieve information from GovUK 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 real-time or current status data about a London Underground line. It is a read-only operation that queries existing data without creating, modifying, deleting, or executing any actions. The blast radius of misuse is minimal—an AI agent could only retrieve unwanted status information, which poses no security or operational risk.
From the tool's definition Tool name 'get_line_status' and description 'Get status for a specific London Underground line' indicate a query operation that retrieves status information with no side effects.
Attacks that exploit this kind of access
Get status for a specific London Underground line. It is categorised as a Read tool in the GovUK MCP Server MCP Server, which means it retrieves data without modifying state.
Register the GovUK MCP Server MCP server in PolicyLayer and add a rule for get_line_status: 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 GovUK MCP Server. Nothing to install.
get_line_status 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_line_status 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_line_status. 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_line_status is provided by the GovUK MCP Server MCP server (stealth-labs-ltd/govuk-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 →