get_kubernetes_cluster_status
A read tool on the Vultr MCP server.
This record as markdown: /tools/rsp2k-mcp-vultr/get-kubernetes-cluster-status.md
What get_kubernetes_cluster_status does on Vultr MCP
AI agents call get_kubernetes_cluster_status 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_status is rated Low
This tool retrieves the current status of a Kubernetes cluster, which is a read-only operation with no side effects. It queries existing state and returns information for inspection. Even if misused by an agent, it cannot modify infrastructure, trigger deployments, delete resources, or move funds. The blast radius is limited to information disclosure.
From the tool's definition Tool name 'get_kubernetes_cluster_status' indicates retrieval of cluster status information. The verb 'get' and noun 'status' are consistent with a read-only query operation.
Attacks that exploit this kind of access
The rule that runs get_kubernetes_cluster_status 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_status, this is the rule to start with:
get_kubernetes_cluster_status 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_status call is checked against it from then on.
Questions about get_kubernetes_cluster_status
get_kubernetes_cluster_status is a read tool on the Vultr MCP server. 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_status: 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_status 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_status 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_status. 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_status 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