AI agents call netdata_query 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.
Querying a chart is a read-only operation that retrieves monitoring or metrics data without causing side effects, modifying state, executing code, or deleting anything. Even if misused by an AI agent, the worst outcome would be information disclosure about system metrics, which has minimal blast radius.
From the tool's definition Tool description states "Query a single chart" - this is a retrieval/querying operation with no modification or execution capabilities. The verb "query" combined with read-only access to chart data indicates data retrieval only.
Documented attack patterns abuse exactly the kind of access netdata_query gives an agent:
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_query:
{
"version": "1",
"default": "deny",
"tools": {
"netdata_query": {}
}
} netdata_query is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
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.
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.