Low Risk

pcap_get_dns

Extract DNS queries and responses from PCAP.

How to control pcap_get_dns ↓

What pcap_get_dns does on Windows Forensics MCP Server

AI agents call pcap_get_dns to retrieve information from Windows Forensics MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

Why pcap_get_dns needs a policy

This tool queries existing PCAP data to retrieve DNS information. It performs forensic analysis of captured traffic without modifying files, executing code, or triggering external operations. The blast radius of misuse is minimal—an agent could extract DNS data from packet captures, which is informational only and does not affect system state, financial obligations, or enable code execution.

From the tool's definition Tool name 'pcap_get_dns' combined with description 'Extract DNS queries and responses from PCAP' indicates passive data retrieval from network packet capture files. The verb 'Extract' and 'get' denote read-only operations with no modification or execution.

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

How to control pcap_get_dns

PolicyLayer is an MCP gateway — it sits between your AI agents and Windows Forensics MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for pcap_get_dns:

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

pcap_get_dns 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 Windows Forensics MCP Server — 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 pcap_get_dns

What does the pcap_get_dns tool do? +

Extract DNS queries and responses from PCAP. It is categorised as a Read tool in the Windows Forensics MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on pcap_get_dns? +

Register the Windows Forensics MCP Server MCP server in PolicyLayer and add a rule for pcap_get_dns: 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 Windows Forensics MCP Server. Nothing to install.

What risk level is pcap_get_dns? +

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

Can I rate-limit pcap_get_dns? +

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

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

pcap_get_dns is provided by the Windows Forensics MCP Server MCP server (x746b/winforensics-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Windows Forensics MCP Server tool call.

Start from Windows Forensics MCP Server, 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.

61 Windows Forensics MCP Server 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.