adguard_stats

Query stats: queries, blocked counts, top clients, top domains, top blocked domains (defaults to last 24h window)

SERVERCrow SOURCEkh0pper/crow

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/kh0pper-crow/adguard-stats.md

WHAT IT DOES

What adguard_stats does on Crow

AI agents call adguard_stats 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.

RISK

Why adguard_stats is rated Low

This tool only reads and retrieves AdGuard statistics and monitoring data. It queries historical data about DNS queries, blocked counts, and top domains/clients, with no ability to modify settings, delete data, or trigger external actions. The default 24-hour window and statistical nature confirm this is purely a Read operation with no side effects or destructive capability.

From the tool's definition Query stats: queries, blocked counts, top clients, top domains, top blocked domains (defaults to last 24h window) - the tool retrieves and queries statistical data with no modification capability

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs adguard_stats 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 adguard_stats, this is the rule to start with:

adguard_stats Allowed

adguard_stats is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "adguard_stats": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Crow, apply this rule, and every adguard_stats call is checked against it from then on.

FAQ

Questions about adguard_stats

What does the adguard_stats tool do? +

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.

How do I enforce a policy on adguard_stats? +

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.

What risk level is adguard_stats? +

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

Can I rate-limit adguard_stats? +

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.

How do I block adguard_stats completely? +

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.

What MCP server provides adguard_stats? +

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.

KEEP EXPLORING

More on Crow, and thousands of servers like it.

This server

All 587 Crow tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →