Check IP addresses from a locally synced PCAP against threat intelligence feeds. Extracts all unique IPs from the capture and checks against URLhaus malware blacklist. Returns list of threatening IPs with severity and context. Sync the PCAP first using wireshark_sync_pcap. Required: pcap_name. Op...
AI agents call wireshark_check_threats 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.
This is a read-only intelligence lookup tool. It extracts IPs from an already-synced PCAP and queries them against external threat databases, returning informational results. There are no side effects, data modifications, or operations triggered beyond querying and returning threat intelligence metadata.
From the tool's definition Tool description states it 'checks against threat intelligence feeds' and 'returns list of threatening IPs' — purely a lookup/query operation. No modification, deletion, or code execution is performed.
Attacks that exploit this kind of access
Check IP addresses from a locally synced PCAP against threat intelligence feeds. Extracts all unique IPs from the capture and checks against URLhaus malware blacklist. Returns list of threatening IPs with severity and context. Sync the PCAP first using wireshark_sync_pcap. Required: pcap_name. Optional: check_urlhaus (default: true). 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 wireshark_check_threats: 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.
wireshark_check_threats 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 wireshark_check_threats 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 wireshark_check_threats. 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.
wireshark_check_threats is provided by the Wireshark MCP Server MCP server (presidio-federal/wireshark-mcp-container). 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 →