get_cluster_totem
Get the corosync totem configuration.
This record as markdown: /tools/gethosthewalrus-proxmox-mcp/get-cluster-totem.md
What get_cluster_totem does on Proxmox MCP Server
AI agents call get_cluster_totem 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_totem is rated Low
This tool retrieves cluster configuration data (corosync totem settings) used for cluster consensus and heartbeat mechanisms. Reading configuration does not modify state, execute commands, or affect infrastructure operations. The blast radius of misuse is minimal — an attacker gains visibility into cluster topology and timing parameters but cannot directly manipulate the cluster or cause harm through the read alone.
From the tool's definition Tool name is 'get_cluster_totem' and description states 'Get the corosync totem configuration' — both indicate a retrieval operation with no modification or execution of external commands.
Attacks that exploit this kind of access
The rule that runs get_cluster_totem 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_totem, this is the rule to start with:
get_cluster_totem 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_totem call is checked against it from then on.
Questions about get_cluster_totem
Get the corosync totem configuration. 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_totem: 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_totem 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_totem 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_totem. 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_totem 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