Check TLS certificate details and security using Python SSL
AI agents call tls_certificate to retrieve information from MCP Recon without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a passive reconnaissance function that queries and analyzes TLS certificate information. It gathers data (certificate chain, validity dates, issuer details, cipher strength) through standard SSL/TLS handshake inspection. No data is created, modified, deleted, or financial transactions are involved.
From the tool's definition The tool checks TLS certificate details and security—certificate inspection is a read-only, passive operation that retrieves and examines existing certificate metadata without modifying, executing code, or triggering side effects.
Documented attack patterns abuse exactly the kind of access tls_certificate gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and MCP Recon, and nothing reaches the server without passing your rules. This is the rule we recommend for tls_certificate:
{
"version": "1",
"default": "deny",
"tools": {
"tls_certificate": {}
}
}tls_certificate is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Check TLS certificate details and security using Python SSL. It is categorised as a Read tool in the MCP Recon MCP Server, which means it retrieves data without modifying state.
Register the MCP Recon MCP server in PolicyLayer and add a rule for tls_certificate: 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 Recon. Nothing to install.
tls_certificate 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_certificate 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_certificate. 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_certificate is provided by the MCP Recon MCP server (sundayz-hunter/mcp_recon). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from MCP Recon, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
13 MCP Recon tools catalogued and risk-classified — across an index of 43,000+ MCP servers.