get_cluster_config_nodes
List nodes configured in the cluster.
This record as markdown: /tools/gethosthewalrus-proxmox-mcp/get-cluster-config-nodes.md
What get_cluster_config_nodes does on Proxmox MCP Server
AI agents call get_cluster_config_nodes to retrieve information from Proxmox MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why get_cluster_config_nodes is rated Low
This tool performs a simple data retrieval operation listing cluster nodes. It has no side effects, does not execute code, does not modify infrastructure, and does not delete or move resources. The blast radius of an AI agent misusing this tool is minimal—an attacker could only gain visibility into cluster topology, which is reconnaissance-level impact.
From the tool's definition Tool name 'get_cluster_config_nodes' and description 'List nodes configured in the cluster' indicate a read-only query operation that retrieves configuration information without modifying, executing operations, or deleting data.
Attacks that exploit this kind of access
The rule that runs get_cluster_config_nodes safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Proxmox MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_cluster_config_nodes, this is the rule to start with:
get_cluster_config_nodes 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 Proxmox MCP Server, apply this rule, and every get_cluster_config_nodes call is checked against it from then on.
Questions about get_cluster_config_nodes
List nodes configured in the cluster. It is categorised as a Read tool in the Proxmox MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Proxmox MCP Server MCP server in PolicyLayer and add a rule for get_cluster_config_nodes: 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 Proxmox MCP Server. Nothing to install.
get_cluster_config_nodes 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_cluster_config_nodes 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_cluster_config_nodes. 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_cluster_config_nodes is provided by the Proxmox MCP Server MCP server (gethosthewalrus/proxmox-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Proxmox MCP Server, and thousands of servers like it.
This server
Across the catalogue