This record as markdown: /tools/creativelead-unclick/urlscan-search.md
What urlscan_search does on UnClick
AI agents call urlscan_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 |
|---|---|---|---|
q | string | — | |
size | number | — | |
api_key | string | — |
Parameters from the server's own tool schema.
Why urlscan_search is rated Low
This tool queries existing scan results from urlscan.io without modifying, deleting, or executing any actions. It is a straightforward read-only operation that retrieves security scan data. The blast radius of misuse is low since it only accesses publicly available or authorized scan data without triggering new operations or state changes.
From the tool's definition Tool name 'urlscan_search' and description 'Search urlscan.io scan results' indicate a query/retrieval operation with no side effects. The word 'search' is a classic Read operation pattern.
Risk signalsHandles credentials or secrets (api_key)
Attacks that exploit this kind of access
The rule that runs urlscan_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 urlscan_search, this is the rule to start with:
urlscan_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 urlscan_search call is checked against it from then on.
Questions about urlscan_search
Search urlscan.io scan results. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
urlscan_search accepts 3 parameters: q, size, api_key. 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_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.
urlscan_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 urlscan_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 urlscan_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.
urlscan_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