This record as markdown: /tools/creativelead-unclick/ptv-search.md
What ptv_search does on UnClick
AI agents call ptv_search 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 | — | |
search_term | string | — |
Parameters from the server's own tool schema.
Why ptv_search is rated Low
This is a search/query operation that retrieves data about public transport (PTV - likely Public Transport Victoria). It queries existing stops, routes, or outlet locations without side effects, modification, deletion, or execution of external operations. The action is read-only information retrieval.
From the tool's definition Tool name 'ptv_search' and description 'Search PTV stops, routes, or outlets' indicate a search operation that retrieves public transportation information without modifying or executing external actions.
Risk signalsHandles credentials or secrets (api_key)
Attacks that exploit this kind of access
The rule that runs ptv_search 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_search, this is the rule to start with:
ptv_search 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_search call is checked against it from then on.
Questions about ptv_search
Search PTV stops, routes, or outlets. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
ptv_search accepts 2 parameters: api_key, search_term. 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_search: 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_search 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_search 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_search. 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_search 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