Low Risk

adguard_query_log

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

How to control adguard_query_log ↓

What adguard_query_log does on Crow

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

Low Risk

Why adguard_query_log needs a policy

adguard_query_log retrieves and displays existing DNS query log entries. It performs no side effects, does not execute commands, does not modify data, and does not delete records. The blast radius is minimal—misuse would only expose DNS query history that has already occurred. This is a straightforward Read operation.

From the tool's definition Tool name and description indicate 'query log' retrieval: 'Returns the last N entries with timestamp, client, question, response, and whether it was blocked.' This is a passive read operation querying historical DNS log data with no modification, deletion, or…

Documented attack patterns abuse exactly the kind of access adguard_query_log gives an agent:

How to control adguard_query_log

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_query_log:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "adguard_query_log": {}
  }
}

adguard_query_log is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Crow — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

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.

Enforce policy on every Crow tool call.

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.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.