urlscan_scan · UnClick MCP: Risk & Policy

WHAT IT DOES

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.

PARAMETERS

Parameter	Type	Required	Description
`url`	string	Yes
`api_key`	string	—
`visibility`	string	—	public, private, or unlisted

Parameters from the server's own tool schema.

WHY IT NEEDS A POLICY

Why urlscan_scan needs a policy

This tool triggers an external operation (submitting a URL to urlscan.io for scanning), which is an action with external side effects. It doesn't merely read data — it initiates a scan job on a third-party service. The blast radius is medium: misuse could result in unintended URLs being scanned and potentially exposing sensitive URLs to a third-party service.

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

Recommended rule Ready

Verdict

urlscan_scan Rate-limited

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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "urlscan_scan": {
      "limits": [
        {
          "counter": "urlscan_scan_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches UnClick, so you can run agents against it safely.

FAQ

Questions about urlscan_scan

What does the urlscan_scan tool do? +

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.

What parameters does urlscan_scan accept? +

urlscan_scan accepts 3 parameters: url, api_key, visibility. Required: url. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on urlscan_scan? +

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.

What risk level is urlscan_scan? +

urlscan_scan is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit urlscan_scan? +

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.

How do I block urlscan_scan completely? +

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.

What MCP server provides urlscan_scan? +

urlscan_scan 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.