Low Risk

scan_ssl_builtin

Check SSL/TLS configuration (built-in).

How to control scan_ssl_builtin ↓

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

Low Risk

SSL/TLS configuration checks are diagnostic operations that query and report on security properties of certificates and protocols. They retrieve data about certificate validity, cipher suites, protocol versions, and related settings. No data is created, modified, deleted, or destroyed; no code is executed on the target; and no financial or external operations are triggered.

From the tool's definition Tool name 'scan_ssl_builtin' and description 'Check SSL/TLS configuration (built-in)' indicate passive information gathering.

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

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

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

scan_ssl_builtin 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 Pentest Ai — 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.

Go deeper

What does the scan_ssl_builtin tool do? +

Check SSL/TLS configuration (built-in). It is categorised as a Read tool in the Pentest Ai MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on scan_ssl_builtin? +

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

What risk level is scan_ssl_builtin? +

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

Can I rate-limit scan_ssl_builtin? +

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

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

scan_ssl_builtin is provided by the Pentest Ai MCP server (0xsteph/pentest-ai). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Pentest Ai tool call.

Deterministic rules across all 51 Pentest Ai tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

51 Pentest Ai tools catalogued and risk-classified — across an index of 42,500+ 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.