adguard_status

AdGuard Home status: version, protection state, upstream DNS servers, filter count, stats summary

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-status.md

WHAT IT DOES

What adguard_status does on Crow

AI agents call adguard_status 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_status is rated Low

This tool queries and returns AdGuard Home status and configuration details without modifying any settings, executing commands, or causing side effects. It is purely informational and belongs in the Read category with low severity.

From the tool's definition Tool name 'adguard_status' and description indicates it retrieves status information: 'version, protection state, upstream DNS servers, filter count, stats summary' — all read-only queries with no side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

adguard_status Allowed

adguard_status 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_status": {}
  }
}

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_status call is checked against it from then on.

FAQ

Questions about adguard_status

What does the adguard_status tool do? +

AdGuard Home status: version, protection state, upstream DNS servers, filter count, stats summary. 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_status? +

Register the Crow MCP server in PolicyLayer and add a rule for adguard_status: 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_status? +

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

Can I rate-limit adguard_status? +

Yes. Add a rate_limit block to the adguard_status 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_status completely? +

Set action: deny in the PolicyLayer policy for adguard_status. 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_status? +

adguard_status 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

claude_git_status on Claude Bridge →get_task_status on 0rca Dojo MCP Server → The MCP Attack Database →

Guides

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