Per-flow RTT statistics from tcp.analysis.ack_rtt.
AI agents call pm_latency_summary 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 performs read-only analysis of network packet capture data to derive latency metrics. It queries existing PCAP data to compute statistics, producing informational output about network performance. There are no side effects, no data modification, and no capability to execute code or commands.
From the tool's definition Tool extracts and summarizes RTT (round-trip time) statistics from PCAP flow data using tcp.analysis.ack_rtt field. The description indicates passive analysis of packet data with no modification, deletion, or execution capabilities.
Attacks that exploit this kind of access
Per-flow RTT statistics from tcp.analysis.ack_rtt. 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_latency_summary: 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_latency_summary 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_latency_summary 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_latency_summary. 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_latency_summary 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 →