This record as markdown: /tools/gethosthewalrus-proxmox-mcp/set-ceph-flags.md
What set_ceph_flags does on Proxmox MCP Server
AI agents invoke set_ceph_flags 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 set_ceph_flags is rated High
Setting a Ceph global flag modifies the operational behavior of the entire Ceph storage cluster (e.g., flags like 'noout', 'norebalance', 'pause' can halt or alter rebalancing, recovery, and I/O operations cluster-wide). This is an Execute/Write action with high blast radius since it affects the distributed storage infrastructure backing all VMs and containers in the Proxmox environment.
From the tool's definition Set a Ceph global flag
Attacks that exploit this kind of access
The rule that runs set_ceph_flags 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 set_ceph_flags, this is the rule to start with:
set_ceph_flags 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 set_ceph_flags call is checked against it from then on.
Questions about set_ceph_flags
Set a Ceph global flag. 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 set_ceph_flags: 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.
set_ceph_flags 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 set_ceph_flags 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 set_ceph_flags. 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.
set_ceph_flags 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