Low Risk

get_daemon_names

Get daemon names by type

How to control get_daemon_names ↓

What get_daemon_names does on Ceph MCP Server

AI agents call get_daemon_names 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_daemon_names needs a policy

This tool retrieves daemon names filtered by type from the Ceph cluster. It performs no side effects, modifications, or operations—purely querying and returning information. The blast radius of misuse is minimal; an AI agent could only gather metadata about cluster daemons, which is already widely known information in typical Ceph deployments. This is a safe informational read operation.

From the tool's definition Tool name is 'get_daemon_names' with description 'Get daemon names by type'. The verb 'Get' and lack of any modification, deletion, or execution language indicates a read-only query operation.

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

How to control get_daemon_names

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

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

get_daemon_names 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_daemon_names

What does the get_daemon_names tool do? +

Get daemon names by type. 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_daemon_names? +

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

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

Can I rate-limit get_daemon_names? +

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

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

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