Manage Azure Kubernetes Service — list, show, get credentials, nodepool listing.
AI agents call az_aks to retrieve information from RedisNexus without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool only retrieves information about Azure Kubernetes Service clusters — listing clusters, showing details, fetching credentials, and listing nodepools. These are read-only operations with no state changes. However, 'get credentials' could expose sensitive kubeconfig/access tokens, raising severity to medium due to potential credential exposure if misused by an AI agent.
From the tool's definition list, show, get credentials, nodepool listing
Attacks that exploit this kind of access
Manage Azure Kubernetes Service — list, show, get credentials, nodepool listing. It is categorised as a Read tool in the RedisNexus MCP Server, which means it retrieves data without modifying state.
Register the RedisNexus MCP server in PolicyLayer and add a rule for az_aks: 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 RedisNexus. Nothing to install.
az_aks 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 az_aks 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 az_aks. 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.
az_aks is provided by the RedisNexus MCP server (rajkumar-madhu/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →