AI agents call query_scans to retrieve information from urlDNA MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Based on naming pattern and sibling tools that include read operations (get_scan, list_queries), this appears to be a retrieval tool that queries existing scan records. The empty description prevents higher confidence, but the verb 'query' combined with read-oriented siblings (get_*, list_*) indicates data retrieval with no modification or destructive capability.
From the tool's definition Tool name 'query_scans' suggests querying or retrieving scan data; aligns with sibling tools 'get_scan' and 'list_queries' which are retrieval operations. Description is empty, reducing specificity.
Documented attack patterns abuse exactly the kind of access query_scans 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 query_scans:
{
"version": "1",
"default": "deny",
"tools": {
"query_scans": {}
}
}query_scans 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.
query_scans. It is categorised as a Read tool in the urlDNA MCP Server MCP Server, which means it retrieves data without modifying state.
Register the urlDNA MCP Server MCP server in PolicyLayer and add a rule for query_scans: 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.
query_scans 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 query_scans 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 query_scans. 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.
query_scans 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.