Search for potential credentials in network traffic (HTTP Basic Auth, FTP, Telnet, etc.)
AI agents call tshark_extract_credentials 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.
Although this tool reveals sensitive information (credentials) and poses high risk if exposed to an untrusted agent, it is fundamentally a Read operation: it searches and extracts data from existing network captures without side effects. The high severity reflects the sensitivity of the data exposed (credentials), not the nature of the operation itself.
From the tool's definition Tool description states it "Search[es] for potential credentials in network traffic" — this is a data retrieval and analysis operation that reads/parses captured packet data without modifying, executing, or deleting anything.
Attacks that exploit this kind of access
Search for potential credentials in network traffic (HTTP Basic Auth, FTP, Telnet, etc.). It is categorised as a Read tool in the Wireshark MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Wireshark MCP Server MCP server in PolicyLayer and add a rule for tshark_extract_credentials: 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.
tshark_extract_credentials 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 tshark_extract_credentials 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 tshark_extract_credentials. 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.
tshark_extract_credentials is provided by the Wireshark MCP Server MCP server (schwarztim/sec-wireshark-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 →