AI agents call list_interfaces to retrieve information from Wireshark MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves information about available network interfaces on the system. While it performs no modifications (ruling out Write, Execute, Destructive, Financial), it does expose system network topology information that could inform reconnaissance activity.
From the tool's definition Tool name 'list_interfaces' and description (translated: 'List all available network interfaces') indicate retrieval of system network interface metadata without modification. This is a read operation that queries system configuration.
Documented attack patterns abuse exactly the kind of access list_interfaces gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Wireshark MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for list_interfaces:
{
"version": "1",
"default": "deny",
"tools": {
"list_interfaces": {}
}
}list_interfaces is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
列出所有可用的网络接口. It is categorised as a Read tool in the Wireshark MCP MCP Server, which means it retrieves data without modifying state.
Register the Wireshark MCP server in PolicyLayer and add a rule for list_interfaces: 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. Nothing to install.
list_interfaces 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 list_interfaces 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 list_interfaces. 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.
list_interfaces is provided by the Wireshark MCP server (jayimu/wireshark_mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Wireshark MCP, 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.
10 Wireshark MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.