Check a URL or domain for malicious activity via URLScan.io. Returns scan verdicts, malicious flag, score, and categories. Args: url_or_domain: URL (https://example.com/path) or bare domain (example.com)
AI agents call check_url_safety to retrieve information from CVE MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a passive lookup tool that queries URL/domain reputation data. It performs no side effects, makes no modifications, executes no code on external systems, and has no financial impact. The worst case of misuse is receiving incorrect security intelligence about a URL, which is a low-severity informational error. It belongs in the Read category.
From the tool's definition Tool 'check_url_safety' retrieves scan verdicts and reputation data from URLScan.io; it queries external security intelligence without modifying, executing, or deleting anything.
Documented attack patterns abuse exactly the kind of access check_url_safety gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and CVE MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for check_url_safety:
{
"version": "1",
"default": "deny",
"tools": {
"check_url_safety": {}
}
}check_url_safety is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Check a URL or domain for malicious activity via URLScan.io. Returns scan verdicts, malicious flag, score, and categories. Args: url_or_domain: URL (https://example.com/path) or bare domain (example.com). It is categorised as a Read tool in the CVE MCP Server MCP Server, which means it retrieves data without modifying state.
Register the CVE MCP Server MCP server in PolicyLayer and add a rule for check_url_safety: 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 CVE MCP Server. Nothing to install.
check_url_safety 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 check_url_safety 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 check_url_safety. 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.
check_url_safety is provided by the CVE MCP Server MCP server (mukul975/cve-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from CVE MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
27 CVE MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.