Execute multiple RadQL queries in parallel for efficiency. Useful for fetching related data from different data types simultaneously (e.g., container details + vulnerabilities + network connections).
AI agents invoke radql_batch_query 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 executes arbitrary RadQL queries against the RAD Security API. While the description emphasizes read-like operations (fetching data), the ability to run arbitrary queries in batch/parallel means it could execute queries with side effects depending on what RadQL supports.
From the tool's definition Execute multiple RadQL queries in parallel... fetching related data from different data types simultaneously
Documented attack patterns abuse exactly the kind of access radql_batch_query 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_batch_query:
{
"version": "1",
"default": "deny",
"tools": {
"radql_batch_query": {
"limits": [
{
"counter": "radql_batch_query_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
} radql_batch_query 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.
Execute multiple RadQL queries in parallel for efficiency. Useful for fetching related data from different data types simultaneously (e.g., container details + vulnerabilities + network connections). 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_batch_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 RAD Security. Nothing to install.
radql_batch_query 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_batch_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 radql_batch_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.
radql_batch_query 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.