update_cluster_options
A write tool on the Proxmox MCP server.
This record as markdown: /tools/gethosthewalrus-proxmox-mcp/update-cluster-options.md
What update_cluster_options does on Proxmox MCP Server
AI agents use update_cluster_options to create or update resources in Proxmox MCP Server, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Proxmox MCP Server environment.
Why update_cluster_options is rated Medium
The tool updates cluster options, which are configuration settings that affect the entire Proxmox cluster. This is a reversible modification (Write category) rather than destructive, executable code, or financial in nature. Severity is high because misconfiguration of cluster options could impact availability, security, or performance across all managed infrastructure.
From the tool's definition Tool name 'update_cluster_options' indicates modification of cluster configuration. Description is empty, limiting direct evidence, but the name and context (Proxmox VE infrastructure management) clearly indicate a write operation that modifies cluster-level…
Attacks that exploit this kind of access
The rule that runs update_cluster_options 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 update_cluster_options, this is the rule to start with:
update_cluster_options stays usable, but capped: an agent stuck in a loop can't make hundreds of changes 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 update_cluster_options call is checked against it from then on.
Questions about update_cluster_options
update_cluster_options is a write tool on the Proxmox MCP Server MCP server. It is categorised as a Write tool in the Proxmox MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Proxmox MCP Server MCP server in PolicyLayer and add a rule for update_cluster_options: 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.
update_cluster_options is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the update_cluster_options 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 update_cluster_options. 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.
update_cluster_options 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