Low Risk

get_stats_from_pcap_file

get_stats_from_pcap_file

How to control get_stats_from_pcap_file ↓

What get_stats_from_pcap_file does on SuricataMCP

AI agents call get_stats_from_pcap_file to retrieve information from SuricataMCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

Why get_stats_from_pcap_file needs a policy

The tool appears to retrieve or query statistical data from network traffic captures. No description is provided, which slightly lowers confidence, but the naming pattern and context of Suricata (a network intrusion detection system) combined with sibling read-only tools strongly suggest this performs data retrieval without side effects.

From the tool's definition Tool name 'get_stats_from_pcap_file' indicates retrieval of statistics from a PCAP (packet capture) file with no modification capability.

Documented attack patterns abuse exactly the kind of access get_stats_from_pcap_file gives an agent:

How to control get_stats_from_pcap_file

PolicyLayer is an MCP gateway — it sits between your AI agents and SuricataMCP, and nothing reaches the server without passing your rules. This is the rule we recommend for get_stats_from_pcap_file:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_stats_from_pcap_file": {}
  }
}

get_stats_from_pcap_file is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register SuricataMCP — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about get_stats_from_pcap_file

What does the get_stats_from_pcap_file tool do? +

get_stats_from_pcap_file. It is categorised as a Read tool in the SuricataMCP MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_stats_from_pcap_file? +

Register the Suricata MCP server in PolicyLayer and add a rule for get_stats_from_pcap_file: 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 SuricataMCP. Nothing to install.

What risk level is get_stats_from_pcap_file? +

get_stats_from_pcap_file is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_stats_from_pcap_file? +

Yes. Add a rate_limit block to the get_stats_from_pcap_file 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.

How do I block get_stats_from_pcap_file completely? +

Set action: deny in the PolicyLayer policy for get_stats_from_pcap_file. 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.

What MCP server provides get_stats_from_pcap_file? +

get_stats_from_pcap_file is provided by the Suricata MCP server (medinios/suricatamcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every SuricataMCP tool call.

Start from SuricataMCP, 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.

4 SuricataMCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.