Low Risk

get_osd_details

Get detailed OSD information

How to control get_osd_details ↓

What get_osd_details does on Ceph MCP Server

AI agents call get_osd_details to retrieve information from Ceph MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

Why get_osd_details needs a policy

This tool retrieves information about Object Storage Daemons (OSDs) in a Ceph cluster. It is a read-only query operation that queries cluster state without side effects. No data is modified, deleted, or executed. The consistent naming pattern across all sibling tools (all prefixed with 'get_') confirms this is part of an informational/monitoring API for Ceph cluster inspection.

From the tool's definition Tool name 'get_osd_details' and description 'Get detailed OSD information' indicate a retrieval operation.

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

How to control get_osd_details

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_details:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_osd_details": {}
  }
}

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

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

Free to start. No card required.

Related tools and policies

Go deeper

Questions about get_osd_details

What does the get_osd_details tool do? +

Get detailed OSD information. 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_details? +

Register the Ceph MCP Server MCP server in PolicyLayer and add a rule for get_osd_details: 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_details? +

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

Can I rate-limit get_osd_details? +

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

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

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

Free to start. No card required.

18 Ceph MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.