run_bruteshark_analysis

What run_bruteshark_analysis does on Pentester-MCP

AI agents invoke run_bruteshark_analysis to trigger actions in Pentester-MCP. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.

Why run_bruteshark_analysis is rated High

This tool executes an external penetration testing utility (Bruteshark) whose effects depend entirely on the input pcap file and analysis parameters provided by the AI agent. While it reads pcap data, the classification hinges on the active execution of analysis logic that processes and extracts intelligence from network traffic—a proactive operation distinct from passive data retrieval.

From the tool's definition Tool name 'run_bruteshark_analysis' indicates execution of Bruteshark, a network traffic analysis tool. Server description states it 'enables AI assistants to autonomously execute over 200 open-source penetration testing tools' including reconnaissance…

The rule that runs run_bruteshark_analysis safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Pentester-MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For run_bruteshark_analysis, this is the rule to start with:

{
  "version": "1",
  "default": "deny",
  "tools": {
    "run_bruteshark_analysis": {
      "limits": [
        {
          "counter": "run_bruteshark_analysis_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

Questions about run_bruteshark_analysis