AI agents call get_container_llm_analysis 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 pre-computed LLM analysis results for a container—a query operation with no side effects. It returns security insights from the RAD Security API without modifying, executing, or deleting any data. Severity is low because misuse would only expose existing analysis data, not trigger destructive or external operations.
From the tool's definition Tool name 'get_container_llm_analysis' and description 'Get LLM analysis of a container' indicate a retrieval operation. The 'get_' prefix and lack of any modification verbs (create, update, delete, etc.) confirm this is a read-only query.
Documented attack patterns abuse exactly the kind of access get_container_llm_analysis 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_llm_analysis:
{
"version": "1",
"default": "deny",
"tools": {
"get_container_llm_analysis": {}
}
}get_container_llm_analysis 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 LLM analysis of a container. 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_llm_analysis: 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_llm_analysis 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_llm_analysis 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_llm_analysis. 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_llm_analysis 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.