get_kubernetes_node_pool
AI agents call get_kubernetes_node_pool to retrieve information from Vultr MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The 'get_' prefix and 'kubernetes_node_pool' context indicate this tool retrieves information about Kubernetes node pool configuration without modifying resources. No write, execute, destructive, or financial operations are implied. Classification as Read is appropriate with moderately high confidence despite empty description.
From the tool's definition Tool name 'get_kubernetes_node_pool' indicates retrieval/query operation; prefix 'get_' is a strong indicator of read-only behavior. Description is empty, limiting confidence slightly.
Documented attack patterns abuse exactly the kind of access get_kubernetes_node_pool gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Vultr MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for get_kubernetes_node_pool:
{
"version": "1",
"default": "deny",
"tools": {
"get_kubernetes_node_pool": {}
}
}get_kubernetes_node_pool 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_kubernetes_node_pool. 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_node_pool: 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_node_pool 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_node_pool 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_node_pool. 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_node_pool 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.
Start from Vultr MCP, 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.
284 Vultr MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.