join_cluster
A execute tool on the Proxmox MCP server.
This record as markdown: /tools/gethosthewalrus-proxmox-mcp/join-cluster.md
What join_cluster does on Proxmox MCP Server
AI agents invoke join_cluster to trigger actions in Proxmox MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
Why join_cluster is rated High
Joining a Proxmox cluster is a significant infrastructure operation that modifies cluster membership, potentially affecting all nodes, VMs, containers, and HA configurations. Based on the tool name and server context (managing Proxmox VE infrastructure), this likely triggers an external operation that reconfigures node membership.
From the tool's definition Tool name 'join_cluster' on a Proxmox VE management server; description is empty and uninformative.
Attacks that exploit this kind of access
The rule that runs join_cluster 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 join_cluster, this is the rule to start with:
join_cluster stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. 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 join_cluster call is checked against it from then on.
Questions about join_cluster
join_cluster is a execute tool on the Proxmox MCP Server MCP server. It is categorised as a Execute tool in the Proxmox MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Proxmox MCP Server MCP server in PolicyLayer and add a rule for join_cluster: 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.
join_cluster is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the join_cluster 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 join_cluster. 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.
join_cluster 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.
Across the catalogue