This record as markdown: /tools/creativelead-unclick/urlscan-scan.md
What urlscan_scan does on UnClick
AI agents invoke urlscan_scan to trigger actions in UnClick. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
| Parameter | Type | Required | Description |
|---|---|---|---|
url | string | — | |
api_key | string | — | |
visibility | string | — | public, private, or unlisted |
Parameters from the server's own tool schema.
Why urlscan_scan is rated High
This tool submits a URL to an external service (urlscan.io) for active scanning, which triggers an external operation — a third-party service visits and analyzes the URL. This is an Execute category action since it initiates an external operation with effects depending on the argument provided. Misuse could expose sensitive URLs or trigger scans of unintended targets.
From the tool's definition Submit a URL for scanning on urlscan.io
Risk signalsAccepts URL/endpoint input (url) · Handles credentials or secrets (api_key)
Attacks that exploit this kind of access
The rule that runs urlscan_scan 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 urlscan_scan, this is the rule to start with:
urlscan_scan stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. 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 urlscan_scan call is checked against it from then on.
Questions about urlscan_scan
Submit a URL for scanning on urlscan.io. It is categorised as a Execute tool in the UnClick MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
urlscan_scan accepts 3 parameters: url, api_key, visibility. 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 urlscan_scan: 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.
urlscan_scan is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the urlscan_scan 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 urlscan_scan. 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.
urlscan_scan 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.
Across the catalogue