Low Risk

get_osd_id

Get all OSD IDs and hosts

How to control get_osd_id ↓

What get_osd_id does on Ceph MCP Server

AI agents call get_osd_id 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_id needs a policy

This tool retrieves metadata about Object Storage Daemon (OSD) identifiers and their associated hosts from the Ceph cluster. It performs no writes, deletions, code execution, or financial operations—it simply queries and returns existing cluster configuration information. Misuse would have minimal impact (information disclosure of cluster topology), making it low severity.

From the tool's definition Tool name 'get_osd_id' and description 'Get all OSD IDs and hosts' indicate data retrieval with no modification. The verb 'Get' and the absence of any mutation, deletion, or side-effect language confirm this is a read-only query operation.

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

How to control get_osd_id

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

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

get_osd_id 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_id

What does the get_osd_id tool do? +

Get all OSD IDs and hosts. 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_id? +

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

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

Can I rate-limit get_osd_id? +

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

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

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