Check if Wireshark/tshark is installed and return version info.
AI agents call check_installation to retrieve information from Mcp Wireshark without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool merely checks the installation status and retrieves version metadata. It is a diagnostic query operation with no side effects, no data modification, no code execution beyond the check itself, and no destructive capability. It belongs in the Read category as a low-severity retrieval operation.
From the tool's definition Tool name 'check_installation' and description indicate it performs a query operation ('Check if Wireshark/tshark is installed and return version info') that retrieves system information without modifying, executing arbitrary code, or causing side effects.
Documented attack patterns abuse exactly the kind of access check_installation gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Mcp Wireshark, and nothing reaches the server without passing your rules. This is the rule we recommend for check_installation:
{
"version": "1",
"default": "deny",
"tools": {
"check_installation": {}
}
} check_installation 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.
Check if Wireshark/tshark is installed and return version info. It is categorised as a Read tool in the Mcp Wireshark MCP Server, which means it retrieves data without modifying state.
Register the Mcp Wireshark MCP server in PolicyLayer and add a rule for check_installation: 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 Mcp Wireshark. Nothing to install.
check_installation 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 check_installation 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 check_installation. 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.
check_installation is provided by the Mcp Wireshark MCP server (khuynh22/mcp-wireshark). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Mcp Wireshark, 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.
13 Mcp Wireshark tools catalogued and risk-classified — across an index of 43,000+ MCP servers.