DHCP transaction analysis with stuck-pattern detection (optional STA MAC).
AI agents call pm_dhcp_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 packet capture data to detect patterns in DHCP transactions. Analysis and detection are read-only operations that query and interpret data without creating, modifying, deleting, or executing side effects. The stuck-pattern detection examines packet sequences but does not alter the PCAP file or trigger external network operations.
From the tool's definition Tool performs 'DHCP transaction analysis with stuck-pattern detection' on PCAP files. The verb 'analysis' and 'detection' indicate data inspection and pattern matching without modification, deletion, or execution of external commands.
Attacks that exploit this kind of access
DHCP transaction analysis with stuck-pattern detection (optional STA MAC). 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_dhcp_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_dhcp_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_dhcp_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_dhcp_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_dhcp_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 →