Helper tool to build RadQL queries programmatically from structured conditions. Useful when you need to construct complex filter or stats queries from structured inputs.
AI agents invoke radql_query_builder to trigger actions in RAD Security. 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 constructs and executes RadQL queries against the RAD Security API. While it may appear to be a query-building helper (Read), it executes programmatically constructed queries that could have broad scope depending on the conditions supplied. The dynamic query construction introduces risk that complex or malformed queries could trigger unintended data exposure or resource-intensive operations.
From the tool's definition 'build RadQL queries programmatically from structured conditions' and 'construct complex filter or stats queries from structured inputs'
Documented attack patterns abuse exactly the kind of access radql_query_builder gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and RAD Security, and nothing reaches the server without passing your rules. This is the rule we recommend for radql_query_builder:
{
"version": "1",
"default": "deny",
"tools": {
"radql_query_builder": {
"limits": [
{
"counter": "radql_query_builder_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
} radql_query_builder 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.
Helper tool to build RadQL queries programmatically from structured conditions. Useful when you need to construct complex filter or stats queries from structured inputs. It is categorised as a Execute tool in the RAD Security MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the RAD Security MCP server in PolicyLayer and add a rule for radql_query_builder: 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 RAD Security. Nothing to install.
radql_query_builder 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 radql_query_builder 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 radql_query_builder. 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.
radql_query_builder is provided by the RAD Security MCP server (rad-security/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from RAD Security, 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.
55 RAD Security tools catalogued and risk-classified — across an index of 43,000+ MCP servers.