ptv_departures
Get PTV departures for a stop. In full UnClick, stop_id can be filled from saved Memory defaults.
This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/ptv-departures.md
What ptv_departures does on UnClick
AI agents call ptv_departures to retrieve information from UnClick without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
api_key | string | — | |
stop_id | number | — | PTV stop ID. Optional when a saved UnClick Memory default exists. |
route_id | number | — | |
route_type | number | — | 0=train, 1=tram, 2=bus, 3=vline, 4=night. Defaults to train. |
max_results | number | — | Defaults to 5, maximum 20. |
direction_id | number | — | |
look_backwards | boolean | — | |
include_cancelled | boolean | — |
Parameters from the server's own tool schema.
Why ptv_departures is rated Low
This tool retrieves real-time or scheduled departure data for a public transport stop without modifying, deleting, or executing external operations. It is a read-only query operation with minimal security impact. The use of saved Memory defaults does not change the nature of the operation. Severity is low as unauthorized access to departure information poses no financial, operational, or privacy risk.
From the tool's definition Tool name 'ptv_departures' and description 'Get PTV departures for a stop' indicate a query operation that retrieves public transport departure information.
Risk signalsHandles credentials or secrets (api_key)
Attacks that exploit this kind of access
The rule that runs ptv_departures safely
PolicyLayer is an MCP gateway: it sits between your AI agents and UnClick, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For ptv_departures, this is the rule to start with:
ptv_departures is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect UnClick, apply this rule, and every ptv_departures call is checked against it from then on.
Questions about ptv_departures
Get PTV departures for a stop. In full UnClick, stop_id can be filled from saved Memory defaults. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
ptv_departures accepts 8 parameters: api_key, stop_id, route_id, route_type, max_results, direction_id, look_backwards, include_cancelled. The full parameter table on this page comes from the server's own tool schema.
Register the UnClick MCP server in PolicyLayer and add a rule for ptv_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 UnClick. Nothing to install.
ptv_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 ptv_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 ptv_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.
ptv_departures is provided by the UnClick MCP server (@unclick/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on UnClick, and thousands of servers like it.
This server
Across the catalogue