url_scan

Scan a URL for phishing, typosquatting, homoglyphs, and malware. Uses VirusTotal (if configured) and heuristic analysis. Returns severity (clean/suspicious/malicious) with detailed risk indicators.

Server Mcp Services san-npm/mcp-services
Category Read
Risk class Low
Parameters 00 required

What url_scan does on Mcp Services

AI agents call url_scan to retrieve information from Mcp Services without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Why url_scan needs a policy

url_scan performs read-only analysis of URL safety characteristics. It queries external services (VirusTotal and heuristics) and returns threat assessment data. No code execution, data modification, deletion, or financial operations occur. The low severity reflects minimal blast radius: misuse would only result in scanning unwanted URLs, with no capability to cause damage or access sensitive systems.

From the tool's definition Tool description states 'Scan a URL for phishing, typosquatting, homoglyphs, and malware' and 'Returns severity (clean/suspicious/malicious) with detailed risk indicators.' This is a security analysis function that retrieves and analyzes threat information…

Questions about url_scan

What does the url_scan tool do? +

Scan a URL for phishing, typosquatting, homoglyphs, and malware. Uses VirusTotal (if configured) and heuristic analysis. Returns severity (clean/suspicious/malicious) with detailed risk indicators. It is categorised as a Read tool in the Mcp Services MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on url_scan? +

Register the Mcp Services MCP server in PolicyLayer and add a rule for url_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 Mcp Services. Nothing to install.

What risk level is url_scan? +

url_scan is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit url_scan? +

Yes. Add a rate_limit block to the url_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 url_scan completely? +

Set action: deny in the PolicyLayer policy for url_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 url_scan? +

url_scan is provided by the Mcp Services MCP server (san-npm/mcp-services). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// LOOK UP ANOTHER SERVER

Every MCP server has a record like this.

Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.