tls.cert-info

Open a live TLS connection to a host and return its certificate: protocol + cipher, chain validity, leaf subject + issuer, valid-from/to, days-until-expiry, serial, SHA-256 fingerprint, SANs, chain length. Active probe; SSRF-guarded. Cert-expiry monitoring, TLS audits.

SERVERMcp SOURCE@2sio/mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-2s-io-mcp/tls.cert-info.md

WHAT IT DOES

What tls.cert-info does on Mcp

AI agents call tls.cert-info 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.

RISK

Why tls.cert-info is rated Low

Although this tool actively probes a remote host (which some might classify as Execute), it is purely informational—retrieving and returning certificate metadata with no side effects on the target system or data. The explicit SSRF-guarding and use cases (cert-expiry monitoring, TLS audits) confirm it is a diagnostic Read operation.

From the tool's definition Tool performs an active network probe to retrieve TLS certificate information from a host (protocol, cipher, chain validity, subject, issuer, validity dates, fingerprint, SANs, chain length).

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs tls.cert-info 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 tls.cert-info, this is the rule to start with:

tls.cert-info Allowed

tls.cert-info is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "tls.cert-info": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Mcp, apply this rule, and every tls.cert-info call is checked against it from then on.

FAQ

Questions about tls.cert-info

What does the tls.cert-info tool do? +

How do I enforce a policy on tls.cert-info? +

Register the MCP server in PolicyLayer and add a rule for tls.cert-info: 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.

What risk level is tls.cert-info? +

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

Can I rate-limit tls.cert-info? +

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

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

tls.cert-info is provided by the MCP server (@2sio/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on , and thousands of servers like it.

This server

All 572 tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →