AI agents call get_tcp_performance to retrieve information from Tshark without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool appears to query and retrieve TCP performance statistics from captured or analyzed network traffic. This is a read operation with no side effects—it does not modify packets, execute commands, delete data, or commit financial transactions. The empty description reduces confidence slightly, but the tool name and context of packet analysis tools strongly suggest passive data retrieval.
From the tool's definition Tool name 'get_tcp_performance' indicates retrieval of TCP performance metrics from network packet data. Empty description limits certainty, but name semantics and sibling tools (analyze_pcap_file, analyze_dns, export_to_json) all perform analysis and data…
Attacks that exploit this kind of access
get_tcp_performance. It is categorised as a Read tool in the Tshark MCP Server, which means it retrieves data without modifying state.
Register the Tshark MCP server in PolicyLayer and add a rule for get_tcp_performance: 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 Tshark. Nothing to install.
get_tcp_performance 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 get_tcp_performance 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 get_tcp_performance. 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.
get_tcp_performance is provided by the Tshark MCP server (ouonet/tshark-mcp). 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 →