AI agents call list_processes 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 retrieve process information without modifying or executing anything. Even though the description is empty and lowers confidence slightly, the name strongly suggests a read operation. In the context of a packet analysis tool, listing processes would be used to correlate network traffic with specific applications—a fundamental Read operation.
From the tool's definition Tool name 'list_processes' indicates enumeration/listing of system processes. Given the server context (TShark network analysis), this likely queries running processes to identify those performing network activity, which is a read-only operation with no side…
Attacks that exploit this kind of access
list_processes. 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 list_processes: 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.
list_processes 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_processes 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_processes. 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_processes 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 →