# tlsScan

Scan TLS/SSL configuration of a domain

Agent View of the PolicyLayer registry record for `tlsScan`. HTML page: https://policylayer.com/tools/com-geekflare-mcp/tlsscan

## Facts

- Tool: `tlsScan`
- Server: Mcp (`@geekflare/mcp`) — https://policylayer.com/tools/com-geekflare-mcp.md
- Install: `npx -y @geekflare/mcp`
- Homepage: https://github.com/oci:geekflarehq/geekflare-api-mcp:0.3.5
- Risk category: Read (Low risk)
- Registry record: grade F, identity unverified
- Server auth posture: open
- Server CORS policy: *
- Server rate-limited: no
- Parameters: 1 (1 required)
- Recommended policy verdict: Allowed

## Parameters

| Parameter | Type | Required | Description |
| --- | --- | --- | --- |
| `url` | string | yes | Target URL |

Parameters from the server's own tool schema.

## Example call (MCP tools/call, JSON-RPC 2.0)

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "tlsScan",
    "arguments": {
      "url": "<url>"
    }
  }
}
```

## Why tlsScan is rated Low

This tool performs passive reconnaissance by querying and analyzing TLS/SSL certificate and configuration data from a domain. It retrieves information about security settings (certificate validity, cipher suites, protocol versions, etc.) without side effects, making network requests to inspect existing infrastructure. No data is created, modified, deleted, or executed—only read and analyzed.

From the tool's own definition: "Tool name 'tlsScan' and description 'Scan TLS/SSL configuration of a domain' indicate data retrieval and inspection of SSL/TLS settings without modifying, executing code, or triggering destructive actions."

Risk signals: Accepts URL/endpoint input (url)

## Use case

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

## Recommended policy (PolicyLayer)

Verdict: **Allowed**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches Mcp:

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "tlsScan": {}
  }
}
```

## Other tools on Mcp (19)

- `lighthouse` — Execute — https://policylayer.com/tools/com-geekflare-mcp/lighthouse.md
- `mtr` — Execute — https://policylayer.com/tools/com-geekflare-mcp/mtr.md
- `openPorts` — Execute — https://policylayer.com/tools/com-geekflare-mcp/openports.md
- `ping` — Execute — https://policylayer.com/tools/com-geekflare-mcp/ping.md
- `url2Pdf` — Execute — https://policylayer.com/tools/com-geekflare-mcp/url2pdf.md
- `brokenLink` — Read — https://policylayer.com/tools/com-geekflare-mcp/brokenlink.md
- `dnsRecord` — Read — https://policylayer.com/tools/com-geekflare-mcp/dnsrecord.md
- `dnsSec` — Read — https://policylayer.com/tools/com-geekflare-mcp/dnssec.md
- `httpHeader` — Read — https://policylayer.com/tools/com-geekflare-mcp/httpheader.md
- `httpProtocol` — Read — https://policylayer.com/tools/com-geekflare-mcp/httpprotocol.md
- `loadTime` — Read — https://policylayer.com/tools/com-geekflare-mcp/loadtime.md
- `metaScrape` — Read — https://policylayer.com/tools/com-geekflare-mcp/metascrape.md
- `mixedContent` — Read — https://policylayer.com/tools/com-geekflare-mcp/mixedcontent.md
- `redirectCheck` — Read — https://policylayer.com/tools/com-geekflare-mcp/redirectcheck.md
- `screenshot` — Read — https://policylayer.com/tools/com-geekflare-mcp/screenshot.md
- `search` — Read — https://policylayer.com/tools/com-geekflare-mcp/search.md
- `siteStatus` — Read — https://policylayer.com/tools/com-geekflare-mcp/sitestatus.md
- `ttfb` — Read — https://policylayer.com/tools/com-geekflare-mcp/ttfb.md
- `webScrape` — Read — https://policylayer.com/tools/com-geekflare-mcp/webscrape.md

## For agents

This record is a snapshot. Live verdicts and the full registry:

- Check every server in your MCP config at once: `npx -y policylayer stack`
- Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md)
- Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events`

---

Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=com-geekflare-mcp · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/com-geekflare-mcp