This record as markdown: /tools/kh0pper-crow/netdata-query.md
What netdata_query does on Crow
AI agents call netdata_query 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_query is rated Low
The tool retrieves or queries data from a monitoring system (netdata charts) without creating, modifying, or deleting data. It has no side effects and matches the 'Read' category definition: retrieves or queries data with no side effects. The blast radius of misuse is minimal—an attacker could only gain visibility into system metrics/charts already available to the Crow service.
From the tool's definition Tool name and description indicate 'Query a single chart' — a retrieval operation with no mutation or execution of external code.
Attacks that exploit this kind of access
The rule that runs netdata_query 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_query, this is the rule to start with:
netdata_query 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_query call is checked against it from then on.
Questions about netdata_query
Query a single chart. 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_query: 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_query 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_query 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_query. 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_query 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