Get k8s audit logs with information about users who shelled into a pod
AI agents call who_shelled_into_pod 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 existing Kubernetes audit log data to provide visibility into shell access events. It does not create, modify, delete, or execute any operations—it only reads and presents historical audit information. This is a classic Read operation with low blast radius, as misuse would only expose information an attacker might already have access to within the cluster.
From the tool's definition Tool name and description indicate retrieval of audit logs: 'Get k8s audit logs with information about users who shelled into a pod'.
Documented attack patterns abuse exactly the kind of access who_shelled_into_pod 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 who_shelled_into_pod:
{
"version": "1",
"default": "deny",
"tools": {
"who_shelled_into_pod": {}
}
}who_shelled_into_pod 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 k8s audit logs with information about users who shelled into a pod. 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 who_shelled_into_pod: 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.
who_shelled_into_pod 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 who_shelled_into_pod 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 who_shelled_into_pod. 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.
who_shelled_into_pod 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.