get_ceph_status_cluster

Get Ceph cluster status (health, monitors, OSDs, PGs).

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-ceph-status-cluster.md

What get_ceph_status_cluster does on Proxmox MCP Server

AI agents call get_ceph_status_cluster 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_ceph_status_cluster is rated Low

This tool retrieves monitoring and status information about the Ceph storage cluster. It performs no mutations, side effects, or destructive operations—it only reads and returns diagnostic data. Misuse by an AI agent would at worst lead to information disclosure or repeated queries, not infrastructure damage or data loss.

From the tool's definition Tool name 'get_ceph_status' and description 'Get Ceph cluster status (health, monitors, OSDs, PGs)' indicate a retrieval operation that queries cluster health metrics and component status without modifying any data.

Questions about get_ceph_status_cluster

What does the get_ceph_status_cluster tool do? +

Get Ceph cluster status (health, monitors, OSDs, PGs). 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_ceph_status_cluster? +

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

What risk level is get_ceph_status_cluster? +

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

Can I rate-limit get_ceph_status_cluster? +

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

How do I block get_ceph_status_cluster completely? +

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

What MCP server provides get_ceph_status_cluster? +

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

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Proxmox MCP Server's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.