Get list of identities for a specific Kubernetes cluster
AI agents call list_identities 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 read-only query to retrieve identity information from a Kubernetes cluster. It returns data without side effects, reversible changes, or irreversible operations. The blast radius is limited since listing identities is informational only and does not execute code, modify data, or affect system state. Low severity is appropriate as this is passive reconnaissance of cluster metadata.
From the tool's definition Tool name 'list_identities' and description 'Get list of identities for a specific Kubernetes cluster' indicate a query operation that retrieves identity information without modification or execution.
Documented attack patterns abuse exactly the kind of access list_identities 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_identities:
{
"version": "1",
"default": "deny",
"tools": {
"list_identities": {}
}
} list_identities 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 list of identities for a specific Kubernetes cluster. 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_identities: 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_identities 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_identities 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_identities. 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_identities 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.