This record as markdown: /tools/creativelead-unclick/ptv-route-directions.md
What ptv_route_directions does on UnClick
AI agents call ptv_route_directions 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 | — | |
route_id | number | — |
Parameters from the server's own tool schema.
Why ptv_route_directions is rated Low
This tool fetches or retrieves directional data for public transport routes (PTV is Public Transport Victoria). It is a read-only operation with no side effects, no code execution, no data modification, and no financial impact. The low severity reflects minimal blast radius even if misused by an AI agent.
From the tool's definition Tool name 'ptv_route_directions' and description 'Get directions for a PTV route' indicate a query operation that retrieves routing information without modifying, executing external operations, or affecting data.
Risk signalsHandles credentials or secrets (api_key)
Attacks that exploit this kind of access
The rule that runs ptv_route_directions 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_route_directions, this is the rule to start with:
ptv_route_directions 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_route_directions call is checked against it from then on.
Questions about ptv_route_directions
Get directions for a PTV route. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
ptv_route_directions accepts 2 parameters: api_key, route_id. 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_route_directions: 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_route_directions 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_route_directions 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_route_directions. 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_route_directions is provided by the UnClick MCP server (creativelead/unclick). 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