ssl_scan · Kali MCP: Risk & Policy

WHAT IT DOES

What ssl_scan does on Kali

AI agents invoke ssl_scan to trigger actions in Kali. 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 IT NEEDS A POLICY

Why ssl_scan needs a policy

SSL/TLS scanning actively probes a remote host's SSL/TLS configuration by initiating connections and testing cipher suites, certificate details, and vulnerabilities. This is an active external operation against a target host. Running on a Kali Linux pentesting server alongside tools like Hydra and SQLMap indicates offensive security context.

From the tool's definition 'Analyze SSL/TLS configuration of a host' on a Kali Linux penetration testing server that integrates tools like Nmap, Nikto, Hydra, and SQLMap

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

ssl_scan Rate-limited

ssl_scan stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

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

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Kali, so you can run agents against it safely.

FAQ

Questions about ssl_scan

What does the ssl_scan tool do? +

Analyze SSL/TLS configuration of a host. It is categorised as a Execute tool in the Kali MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on ssl_scan? +

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

What risk level is ssl_scan? +

ssl_scan is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit ssl_scan? +

Yes. Add a rate_limit block to the ssl_scan 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 ssl_scan completely? +

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

ssl_scan is provided by the Kali MCP server (rangta10/kali-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// THE FULL RECORD

ssl_scan is one line of Kali's registry record.

The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.

Teams ship this data inside their own products. See what a licence covers →