AI agents invoke new_scan to trigger actions in urlDNA MCP Server. 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.
This tool likely triggers a scan operation against a URL, which is an execute action—it runs an external operation (threat scan) whose effects depend on the URL argument provided. While scanning itself is not destructive or financial, it executes an external service call. Confidence is moderate (0.75) because the description is empty, requiring inference from context and naming convention.
From the tool's definition Tool name 'new_scan' combined with server context showing URL scanning and threat detection capabilities indicates triggering an external security scanning operation. The tool name suggests initiating a new scan action on the urlDNA platform.
Documented attack patterns abuse exactly the kind of access new_scan gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and urlDNA MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for new_scan:
{
"version": "1",
"default": "deny",
"tools": {
"new_scan": {
"limits": [
{
"counter": "new_scan_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}new_scan 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.
Free to start. No card required.
new_scan. It is categorised as a Execute tool in the urlDNA MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the urlDNA MCP Server MCP server in PolicyLayer and add a rule for new_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 urlDNA MCP Server. Nothing to install.
new_scan 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 new_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.
Set action: deny in the PolicyLayer policy for new_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.
new_scan is provided by the urlDNA MCP Server MCP server (urldna/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from urlDNA 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.
14 urlDNA MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.