AI agents call delete_query to permanently remove resources in urlDNA MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
The tool name 'delete_query' clearly indicates permanent deletion of query records. Deletion is irreversible and falls under Destructive actions. High severity reflects that an AI agent misusing this could lose important threat intelligence queries or analysis records.
From the tool's definition Tool name is 'delete_query' with an empty description. The verb 'delete' indicates irreversible removal of data (a query object in the urlDNA threat intelligence platform). No description provided to clarify scope or reversibility.
Documented attack patterns abuse exactly the kind of access delete_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 delete_query:
{
"version": "1",
"default": "deny",
"hide": [
"delete_query"
]
}delete_query disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.
Free to start. No card required.
delete_query. It is categorised as a Destructive tool in the urlDNA MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the urlDNA MCP Server MCP server in PolicyLayer and add a rule for delete_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.
delete_query is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the delete_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 delete_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.
delete_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.