DNS query/response analysis, top names, and failure samples (optional client IP).
AI agents call pm_dns_analysis to retrieve information from PacketMaster without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool analyzes existing network traffic data captured in PCAP files to extract DNS statistics and patterns. It queries and examines data (DNS lookups, response codes, query statistics) but does not create, modify, delete, or execute code. The optional client IP parameter is used only for filtering analysis results, not for side effects.
From the tool's definition Tool performs 'DNS query/response analysis, top names, and failure samples' - these are analytical and diagnostic operations that retrieve and examine network data without modification.
Attacks that exploit this kind of access
DNS query/response analysis, top names, and failure samples (optional client IP). It is categorised as a Read tool in the PacketMaster MCP Server, which means it retrieves data without modifying state.
Register the PacketMaster MCP server in PolicyLayer and add a rule for pm_dns_analysis: 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 PacketMaster. Nothing to install.
pm_dns_analysis 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 pm_dns_analysis 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 pm_dns_analysis. 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.
pm_dns_analysis is provided by the PacketMaster MCP server (jctechbr/packetmaster). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →