Get detailed information about a container secured by RAD Security
AI agents call get_container_details 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 retrieves and queries container information from the RAD Security platform. It performs a read-only operation that returns existing data without creating, modifying, deleting, or executing any changes. The blast radius is minimal—misuse would result in unauthorized information disclosure rather than operational impact or data destruction.
From the tool's definition Tool name 'get_container_details' and description 'Get detailed information about a container secured by RAD Security' indicate a query/retrieval operation with no side effects.
Documented attack patterns abuse exactly the kind of access get_container_details 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 get_container_details:
{
"version": "1",
"default": "deny",
"tools": {
"get_container_details": {}
}
}get_container_details 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.
Get detailed information about a container secured by RAD Security. 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 get_container_details: 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.
get_container_details 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 get_container_details 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 get_container_details. 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.
get_container_details 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.