Query stats: queries, blocked counts, top clients, top domains, top blocked domains (defaults to last 24h window)
AI agents call adguard_stats 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.
This tool retrieves and queries statistical data from AdGuard with no side effects. It performs passive data retrieval operations (queries, counts, top lists) within a time window. There is no capability to modify settings, execute commands, delete data, or perform financial transactions. The default 24h window is a read-only parameter. This is a straightforward Read category tool with minimal risk.
From the tool's definition Tool description states 'Query stats' and lists only retrieval operations: 'queries, blocked counts, top clients, top domains, top blocked domains'. No modification, deletion, execution, or financial operations are mentioned.
Documented attack patterns abuse exactly the kind of access adguard_stats 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 adguard_stats:
{
"version": "1",
"default": "deny",
"tools": {
"adguard_stats": {}
}
} adguard_stats 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 stats: queries, blocked counts, top clients, top domains, top blocked domains (defaults to last 24h window). 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 adguard_stats: 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.
adguard_stats 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 adguard_stats 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 adguard_stats. 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.
adguard_stats 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.