This record as markdown: /tools/com-geekflare-mcp/tlsscan.md
What tlsScan does on Mcp
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.
| Parameter | Type | Required | Description |
|---|---|---|---|
url | string | Yes | Target URL |
Parameters from the server's own tool schema.
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 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 signalsAccepts URL/endpoint input (url)
Attacks that exploit this kind of access
The rule that runs tlsScan safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Mcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For tlsScan, this is the rule to start with:
tlsScan is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Mcp, apply this rule, and every tlsScan call is checked against it from then on.
Questions about tlsScan
Scan TLS/SSL configuration of a domain. It is categorised as a Read tool in the Mcp MCP Server, which means it retrieves data without modifying state.
tlsScan accepts 1 parameter: url. Required: url. The full parameter table on this page comes from the server's own tool schema.
Register the MCP server in PolicyLayer and add a rule for tlsScan: 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 Mcp. Nothing to install.
tlsScan is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the tlsScan 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.
Set action: deny in the PolicyLayer policy for tlsScan. 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.
tlsScan is provided by the MCP server (@geekflare/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on , and thousands of servers like it.
This server
Across the catalogue