get_cluster_config

Get the current cluster configuration (corosync, nodes, join info).

SERVERProxmox MCP Server SOURCEgethosthewalrus/proxmox-mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/gethosthewalrus-proxmox-mcp/get-cluster-config.md

WHAT IT DOES

What get_cluster_config does on Proxmox MCP Server

AI agents call get_cluster_config 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.

RISK

Why get_cluster_config is rated Low

This tool only retrieves and queries the current state of cluster configuration metadata (corosync, nodes, join info). It has no side effects, does not modify data, execute commands, or delete resources. It falls squarely into the Read category.

From the tool's definition Tool name is 'get_cluster_config' and description states 'Get the current cluster configuration' — a retrieval operation with no modification or execution of infrastructure changes.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs get_cluster_config 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, this is the rule to start with:

get_cluster_config Allowed

get_cluster_config is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_cluster_config": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Proxmox MCP Server, apply this rule, and every get_cluster_config call is checked against it from then on.

FAQ

Questions about get_cluster_config

What does the get_cluster_config tool do? +

Get the current cluster configuration (corosync, nodes, join info). It is categorised as a Read tool in the Proxmox MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_cluster_config? +

Register the Proxmox MCP Server MCP server in PolicyLayer and add a rule for get_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 Proxmox MCP Server. Nothing to install.

What risk level is get_cluster_config? +

get_cluster_config is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_cluster_config? +

Yes. Add a rate_limit block to the get_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.

How do I block get_cluster_config completely? +

Set action: deny in the PolicyLayer policy for get_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.

What MCP server provides get_cluster_config? +

get_cluster_config 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.

KEEP EXPLORING

More on Proxmox MCP Server, and thousands of servers like it.

This server

All 286 Proxmox MCP Server tools →

Across the catalogue

get_cocktail_by_category on Cocktails RAG MCP Server →get_torrent_detail on M-Team MCP Server →aiva_get_affiliate on AIVA MCP Server →get-chuck-categories on Jokes MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →