This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/ptv-disruptions.md
What ptv_disruptions does on UnClick
AI agents call ptv_disruptions 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_types | string | — |
Parameters from the server's own tool schema.
Why ptv_disruptions is rated Low
The tool retrieves current service disruption information from PTV (Public Transport Victoria). This is a read-only operation that queries existing data without creating, modifying, deleting, or executing any code. The blast radius of misuse is minimal—an agent could only retrieve publicly available transport disruption data. No financial, destructive, or execute capabilities are evident.
From the tool's definition Tool name 'ptv_disruptions' and description 'Get current PTV service disruptions' indicate a query/retrieval operation with no state-modifying side effects.
Risk signalsHandles credentials or secrets (api_key)
Attacks that exploit this kind of access
The rule that runs ptv_disruptions 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_disruptions, this is the rule to start with:
ptv_disruptions 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_disruptions call is checked against it from then on.
Questions about ptv_disruptions
Get current PTV service disruptions. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
ptv_disruptions accepts 2 parameters: api_key, route_types. 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_disruptions: 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_disruptions 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_disruptions 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_disruptions. 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_disruptions 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