AI agents use create_query to create or update resources in urlDNA MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your urlDNA MCP Server environment.
The tool creates new data records (queries) in the threat intelligence system, which is reversible through 'delete_query'. This is a Write operation—it modifies the system state by adding new data. Severity is medium because misuse could flood the platform with unwanted queries or consume resources, but the operation is not destructive or financial in nature.
From the tool's definition Tool name 'create_query' indicates data creation. Sibling tools include 'delete_query' and 'get_query', establishing a clear CRUD pattern where 'create_query' creates new query records in the urlDNA threat intelligence platform.
Documented attack patterns abuse exactly the kind of access create_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 create_query:
{
"version": "1",
"default": "deny",
"tools": {
"create_query": {
"limits": [
{
"counter": "create_query_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}create_query stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
create_query. It is categorised as a Write tool in the urlDNA MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the urlDNA MCP Server MCP server in PolicyLayer and add a rule for create_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.
create_query is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the create_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 create_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.
create_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.