Real-time predicted departures from a Metlink stop.
AI agents call next_departures to retrieve information from Wellington Transport Assistant without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries public transit data without side effects. It returns departure predictions for a specified stop, which is a straightforward read operation. The data is public and immutable from the user's perspective. No code execution, financial transactions, or destructive actions are possible.
From the tool's definition Tool retrieves 'real-time predicted departures' from a public transport stop. The verb is 'get' (implied by 'Provides tools to... get next departures'), and the description contains only read-oriented language: 'retrieves', 'queries', 'real-time data'.
Attacks that exploit this kind of access
Real-time predicted departures from a Metlink stop. It is categorised as a Read tool in the Wellington Transport Assistant MCP Server, which means it retrieves data without modifying state.
Register the Wellington Transport Assistant MCP server in PolicyLayer and add a rule for next_departures: 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 Wellington Transport Assistant. Nothing to install.
next_departures 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 next_departures 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 next_departures. 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.
next_departures is provided by the Wellington Transport Assistant MCP server (sdhilip200/metlink-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 →