get_kubernetes_cluster_config
Get the kubeconfig for a Kubernetes cluster.
This record as markdown: /tools/rsp2k-mcp-vultr/get-kubernetes-cluster-config.md
What get_kubernetes_cluster_config does on Vultr MCP
AI agents call get_kubernetes_cluster_config to retrieve information from Vultr MCP without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why get_kubernetes_cluster_config is rated Low
This tool performs a read operation by fetching cluster credentials/configuration. However, severity is rated 'high' rather than 'low' because the kubeconfig contains sensitive authentication material that grants administrative access to a Kubernetes cluster. Unauthorized disclosure could enable cluster compromise, though the tool itself does not execute commands or modify infrastructure—it only retrieves data.
From the tool's definition Tool retrieves kubeconfig for a Kubernetes cluster via 'Get the kubeconfig' action, which is a read/retrieval operation without data modification.
Attacks that exploit this kind of access
The rule that runs get_kubernetes_cluster_config safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Vultr MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_kubernetes_cluster_config, this is the rule to start with:
get_kubernetes_cluster_config is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Vultr MCP, apply this rule, and every get_kubernetes_cluster_config call is checked against it from then on.
Questions about get_kubernetes_cluster_config
Get the kubeconfig for a Kubernetes cluster. It is categorised as a Read tool in the Vultr MCP MCP Server, which means it retrieves data without modifying state.
Register the Vultr MCP server in PolicyLayer and add a rule for get_kubernetes_cluster_config: 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 Vultr MCP. Nothing to install.
get_kubernetes_cluster_config 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_kubernetes_cluster_config 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_kubernetes_cluster_config. 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_kubernetes_cluster_config is provided by the Vultr MCP server (rsp2k/mcp-vultr). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Vultr, and thousands of servers like it.
This server
Across the catalogue