netdata_alarms
List Netdata alarms. By default returns only raised (warning/critical) alarms.
This record as markdown: /tools/kh0pper-crow/netdata-alarms.md
What netdata_alarms does on Crow
AI agents call netdata_alarms to retrieve information from Crow without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why netdata_alarms is rated Low
This tool queries and retrieves existing alarm information from a monitoring system (Netdata). It performs no mutations, deletions, code execution, or financial operations. The worst-case misuse would be information disclosure about system alerts, which is low-severity. Confidence is high because the description is clear and explicit about its read-only nature.
From the tool's definition Tool name 'netdata_alarms' and description 'List Netdata alarms' indicate retrieval of alarm data with no modification. The phrase 'By default returns only raised (warning/critical) alarms' confirms this is a query/list operation with no side effects.
Attacks that exploit this kind of access
The rule that runs netdata_alarms safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Crow, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For netdata_alarms, this is the rule to start with:
netdata_alarms is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Crow, apply this rule, and every netdata_alarms call is checked against it from then on.
Questions about netdata_alarms
List Netdata alarms. By default returns only raised (warning/critical) alarms. It is categorised as a Read tool in the Crow MCP Server, which means it retrieves data without modifying state.
Register the Crow MCP server in PolicyLayer and add a rule for netdata_alarms: 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.
netdata_alarms is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the netdata_alarms 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.
Set action: deny in the PolicyLayer policy for netdata_alarms. 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.
netdata_alarms 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.
More on Crow, and thousands of servers like it.
This server
Across the catalogue