List possible values for a filter field (e.g., namespace list, cluster list, severity values). Useful for building dynamic filters when you need to know available enum-like values. Call this when constructing filters that need specific values.
AI agents call radql_list_filter_values to retrieve information from RAD Security without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool queries available filter values (namespaces, clusters, severity levels, etc.) from the RAD Security API to support filter construction. This is a pure read operation that retrieves metadata about available options without modifying, deleting, or executing any operations. The limited scope and informational nature of the data returned make this low severity.
From the tool's definition Tool description states it 'List possible values for a filter field' and is 'Useful for building dynamic filters when you need to know available enum-like values.' This is a retrieval operation with no side effects.
Documented attack patterns abuse exactly the kind of access radql_list_filter_values 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_list_filter_values:
{
"version": "1",
"default": "deny",
"tools": {
"radql_list_filter_values": {}
}
}radql_list_filter_values 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.
List possible values for a filter field (e.g., namespace list, cluster list, severity values). Useful for building dynamic filters when you need to know available enum-like values. Call this when constructing filters that need specific values. It is categorised as a Read tool in the RAD Security MCP Server, which means it retrieves data without modifying state.
Register the RAD Security MCP server in PolicyLayer and add a rule for radql_list_filter_values: 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_list_filter_values 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 radql_list_filter_values 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_list_filter_values. 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_list_filter_values 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.