cluster_get_kubeconfig
AI agents call cluster_get_kubeconfig to retrieve information from GreenNode MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
While the tool retrieves data (Read category), kubeconfig files contain sensitive authentication tokens and certificates that could grant significant cluster access if exposed. This elevates severity to medium despite the read-only nature. Confidence is moderate (0.75) because the description is empty and classification relies on name inference and context from sibling tools.
From the tool's definition Tool name 'cluster_get_kubeconfig' indicates retrieval of Kubernetes cluster configuration credentials. The 'get' action and context of sibling tools managing VNG Cloud infrastructure suggest read-only access to sensitive cluster credentials.
Attacks that exploit this kind of access
cluster_get_kubeconfig. It is categorised as a Read tool in the GreenNode MCP Server MCP Server, which means it retrieves data without modifying state.
Register the GreenNode MCP Server MCP server in PolicyLayer and add a rule for cluster_get_kubeconfig: 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 GreenNode MCP Server. Nothing to install.
cluster_get_kubeconfig 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 cluster_get_kubeconfig 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 cluster_get_kubeconfig. 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.
cluster_get_kubeconfig is provided by the GreenNode MCP Server MCP server (vngcloud/greennode-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 →