Low Risk

netdata_status

Netdata agent status: version, hostname, uptime, chart count, raised-alarm count

How to control netdata_status ↓

What netdata_status does on Crow

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

Low Risk

Why netdata_status needs a policy

This tool only queries and retrieves existing system status data from the Netdata agent. It performs no write, delete, execute, or financial operations. The information returned is read-only and does not alter any state or trigger external operations. Low severity because the exposed data is non-sensitive system metrics typical of monitoring tools.

From the tool's definition Tool retrieves status information (version, hostname, uptime, chart count, raised-alarm count) with no modification or side effects. The verb 'status' indicates a query operation returning system metrics.

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

How to control netdata_status

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

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

netdata_status 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 Crow — 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 netdata_status

What does the netdata_status tool do? +

Netdata agent status: version, hostname, uptime, chart count, raised-alarm count. It is categorised as a Read tool in the Crow MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on netdata_status? +

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

What risk level is netdata_status? +

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

Can I rate-limit netdata_status? +

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

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

netdata_status is provided by the Crow MCP server (kh0pper/crow). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Crow tool call.

Start from Crow, 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.

576 Crow 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.