adguard_query_log

Recent DNS queries. Returns the last N entries with timestamp, client, question, response, and whether it was blocked.

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-query-log.md

WHAT IT DOES

What adguard_query_log does on Crow

AI agents call adguard_query_log 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_query_log is rated Low

This is a read-only query tool that retrieves historical DNS query logs. While it doesn't modify data, it poses medium severity because DNS logs can reveal sensitive information about network activity, user browsing patterns, and client behavior, which could be misused by an AI agent to profile network users or identify infrastructure details.

From the tool's definition Tool description states it "Returns the last N entries with timestamp, client, question, response, and whether it was blocked" — a retrieval operation with no modification or deletion of data.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

adguard_query_log Allowed

adguard_query_log 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_query_log": {}
  }
}

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

FAQ

Questions about adguard_query_log

What does the adguard_query_log tool do? +

Recent DNS queries. Returns the last N entries with timestamp, client, question, response, and whether it was blocked. 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_query_log? +

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

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

Can I rate-limit adguard_query_log? +

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

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

adguard_query_log 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_query on Claude Bridge → The MCP Attack Database →

Guides

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