Low Risk

list_tcp_streams

list_tcp_streams

How to control list_tcp_streams ↓

What list_tcp_streams does on Wireshark MCP Server

AI agents call list_tcp_streams to retrieve information from Wireshark 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 list_tcp_streams needs a policy

The tool appears to list/enumerate TCP streams, which is a read operation that retrieves network metadata. While the description is empty (lowering confidence slightly), the name and context of sibling analysis tools strongly suggest this is a querying/enumeration function.

From the tool's definition Tool named 'list_tcp_streams' with no description provided. Based on naming convention and sibling tools (follow_tcp_stream, analyze_pcap_file, capture_live_packets), this tool retrieves or enumerates TCP stream information from network captures without…

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

How to control list_tcp_streams

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

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

list_tcp_streams 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 Wireshark 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 list_tcp_streams

What does the list_tcp_streams tool do? +

list_tcp_streams. It is categorised as a Read tool in the Wireshark MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on list_tcp_streams? +

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

What risk level is list_tcp_streams? +

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

Can I rate-limit list_tcp_streams? +

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

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

list_tcp_streams is provided by the Wireshark MCP Server MCP server (mixelpixx/wireshark-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Wireshark MCP Server tool call.

Start from Wireshark 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.

19 Wireshark 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.