virustotal_scan_url
Submit a URL for scanning on VirusTotal.
This record as markdown: /tools/creativelead-unclick/virustotal-scan-url.md
What virustotal_scan_url does on UnClick
AI agents invoke virustotal_scan_url 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 | — |
Parameters from the server's own tool schema.
Why virustotal_scan_url is rated High
This tool submits a URL to an external service (VirusTotal) for scanning, which triggers an external operation. It's not a simple read/query of existing data — it actively initiates a new scan job on a third-party platform. The blast radius is medium: misuse could cause unintended URLs to be submitted for scanning, potentially leaking sensitive URLs to VirusTotal's platform, but it does not delete data or move money.
From the tool's definition Submit a URL for scanning on VirusTotal
Risk signalsAccepts URL/endpoint input (url) · Handles credentials or secrets (api_key)
Attacks that exploit this kind of access
The rule that runs virustotal_scan_url 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 virustotal_scan_url, this is the rule to start with:
virustotal_scan_url 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 virustotal_scan_url call is checked against it from then on.
Questions about virustotal_scan_url
Submit a URL for scanning on VirusTotal. 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.
virustotal_scan_url accepts 2 parameters: url, 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 virustotal_scan_url: 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.
virustotal_scan_url 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 virustotal_scan_url 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 virustotal_scan_url. 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.
virustotal_scan_url 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