AI agents call get_query 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.
This tool retrieves or queries existing data without modification. The 'get_' prefix consistently indicates a read operation across this MCP server. No description was provided, which slightly lowers confidence, but the naming convention and server context strongly suggest data retrieval only.
From the tool's definition Tool name 'get_query' follows the retrieval pattern (get_*), and context shows sibling tools like 'list_queries', 'list_brands', 'get_brand', and 'get_scan' which are clearly read operations. Server is threat intelligence platform for scanning/analysis.
Documented attack patterns abuse exactly the kind of access get_query 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 get_query:
{
"version": "1",
"default": "deny",
"tools": {
"get_query": {}
}
} get_query 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.
get_query. 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 get_query: 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.
get_query 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 get_query 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 get_query. 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.
get_query 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.