get_osd_summary

THE RISK

Low Risk

Why get_osd_summary needs a policy

This is a read-only query tool that retrieves summary information about OSDs in a Ceph cluster. It has no side effects, does not modify state, execute commands, or affect financial operations. The blast radius of misuse is minimal—an agent could only gather information about the storage cluster's status.

From the tool's definition Tool name 'get_osd_summary' and description 'Get cluster OSD summary' indicate a retrieval operation. The verb 'get' and context of querying cluster state (OSD = Object Storage Daemon) show this retrieves monitoring/status data without modification.

Documented attack patterns abuse exactly the kind of access get_osd_summary gives an agent:

POLICY

How to control get_osd_summary

PolicyLayer is an MCP gateway — it sits between your AI agents and Ceph MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for get_osd_summary:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_osd_summary": {}
  }
}

get_osd_summary is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

Create a free account and register Ceph MCP Server — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

CAP THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Ceph MCP Server tools

Execute perform_daemon_action Perform action on daemon Execute perform_osd_mark_action Mark OSD in/out status Read get_cluster_capacity Get cluster capacity summary including total objects and capacity statistics Read get_daemon_details Get detailed daemon information Read get_daemon_names Get daemon names by type Read get_daemon_summary Get cluster daemon summary Read get_fs_details Get detailed information about a specific CephFS filesystem Read get_fs_summary Get CephFS filesystem summary

All 18 Ceph MCP Server tools →

Read tools on other servers

M-Team MCP Server get_torrent_detail YouTube MCP Server search_channel Android Forensics ADB MCP Server parse_browser_history 0xarchive web3_challenge

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Data exfiltration → How read access becomes an exfiltration channel when chained with untrusted content.
MCP token cost → What connecting this server costs in context-window tokens on every request.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about get_osd_summary

What does the get_osd_summary tool do? +

Get cluster OSD summary. It is categorised as a Read tool in the Ceph MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_osd_summary? +

Register the Ceph MCP Server MCP server in PolicyLayer and add a rule for get_osd_summary: 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 Ceph MCP Server. Nothing to install.

What risk level is get_osd_summary? +

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

Can I rate-limit get_osd_summary? +

Yes. Add a rate_limit block to the get_osd_summary 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_osd_summary completely? +

Set action: deny in the PolicyLayer policy for get_osd_summary. 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_osd_summary? +

get_osd_summary is provided by the Ceph MCP Server MCP server (rajmohanram/ceph-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Ceph MCP Server tool call.

Start from Ceph MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →