run_sslscan

What run_sslscan does on Pentester-MCP

AI agents invoke run_sslscan 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_sslscan is rated High

While sslscan is primarily a scanning tool (typically Read), it is exposed here as part of a penetration testing server where tools are explicitly designed for autonomous execution by AI agents. The tool name alone lacks descriptive detail (empty description), but contextual evidence from the server's purpose and sibling Execute-category tools strongly indicates this runs a scanning command.

From the tool's definition Tool name 'run_sslscan' indicates execution of sslscan, a penetration testing tool for SSL/TLS scanning. Server description confirms this is a penetration testing MCP that 'autonomously execute[s] over 200 open-source penetration testing tools' and lists…

The rule that runs run_sslscan 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_sslscan, this is the rule to start with:

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

Questions about run_sslscan