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.
AI agents call tls.cert-info to retrieve information from Mcp without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
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
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. It is categorised as a Read tool in the Mcp MCP Server, which means it retrieves data without modifying state.
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.
tls.cert-info 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 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.
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.
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.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →