List containers secured by RAD Security with optional filtering by image name, image digest, namespace, cluster_id, or free text search
AI agents call list_containers 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.
This tool performs a query operation that retrieves container information from the RAD Security system with optional filters. It has no side effects, does not modify data, execute code, delete anything, or commit financial actions. It is purely informational retrieval, making it a Read category tool with low severity.
From the tool's definition Tool name is 'list_containers' and description states it 'List containers secured by RAD Security with optional filtering' - this is a retrieval operation with no modification or deletion of data.
Documented attack patterns abuse exactly the kind of access list_containers 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 list_containers:
{
"version": "1",
"default": "deny",
"tools": {
"list_containers": {}
}
}list_containers 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 containers secured by RAD Security with optional filtering by image name, image digest, namespace, cluster_id, or free text search. 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 list_containers: 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.
list_containers 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 list_containers 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 list_containers. 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.
list_containers 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.