urlscan_get_result
Get the result of a urlscan.io scan by UUID.
This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/urlscan-get-result.md
What urlscan_get_result does on UnClick
AI agents call urlscan_get_result 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 |
|---|---|---|---|
uuid | string | Yes | |
api_key | string | — |
Parameters from the server's own tool schema.
Why urlscan_get_result is rated Low
This tool retrieves previously-generated scan results from urlscan.io using a UUID identifier. The 'Get' verb and read-only nature indicate it only queries and returns data without side effects. The severity is low because it accesses security scan metadata that is already public or associated with the UUID, posing minimal risk of misuse by an AI agent.
From the tool's definition Tool description states 'Get the result of a urlscan.io scan by UUID' — a retrieval operation with no modification or destructive capability.
Risk signalsHandles credentials or secrets (api_key)
Attacks that exploit this kind of access
The rule that runs urlscan_get_result 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_get_result, this is the rule to start with:
urlscan_get_result 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_get_result call is checked against it from then on.
Questions about urlscan_get_result
Get the result of a urlscan.io scan by UUID. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
urlscan_get_result accepts 2 parameters: uuid, api_key. Required: uuid. 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_get_result: 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_get_result 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_get_result 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_get_result. 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_get_result 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