AdGuard Home status: version, protection state, upstream DNS servers, filter count, stats summary
AI agents call adguard_status 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 performs read-only queries to fetch the current state and configuration of AdGuard Home. It returns status data and metrics without creating, modifying, deleting, or executing any operations. The blast radius of misuse is minimal since the tool cannot affect system behavior or cause data loss.
From the tool's definition Tool retrieves AdGuard Home status information including version, protection state, upstream DNS servers, filter count, and stats summary—purely informational queries with no data modification or external side effects.
Documented attack patterns abuse exactly the kind of access adguard_status 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_status:
{
"version": "1",
"default": "deny",
"tools": {
"adguard_status": {}
}
} adguard_status 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.
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.
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.
adguard_status 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_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.
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.
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.
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.