tools_ssl_check
Free public API. Check the TLS certificate of any public hostname. Returns issuer, subject, validity dates, days until expiry, full chain, cipher, protocol, and SAN list. No Bearer required.
This record as markdown: /tools/dev-domainee-domainee/tools-ssl-check.md
What tools_ssl_check does on Domainee
AI agents call tools_ssl_check to retrieve information from Domainee 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 |
|---|---|---|---|
host | string | Yes | Hostname to check. Optionally with port, e.g. example.com:443. |
Parameters from the server's own tool schema.
Why tools_ssl_check is rated Low
Even though tools_ssl_check only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Risk signalsAccepts URL/endpoint input (host)
Attacks that exploit this kind of access
The rule that runs tools_ssl_check safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Domainee, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For tools_ssl_check, this is the rule to start with:
tools_ssl_check 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 Domainee, apply this rule, and every tools_ssl_check call is checked against it from then on.
Questions about tools_ssl_check
Free public API. Check the TLS certificate of any public hostname. Returns issuer, subject, validity dates, days until expiry, full chain, cipher, protocol, and SAN list. No Bearer required. It is categorised as a Read tool in the Domainee MCP Server, which means it retrieves data without modifying state.
tools_ssl_check accepts 1 parameter: host. Required: host. The full parameter table on this page comes from the server's own tool schema.
Register the Domainee MCP server in PolicyLayer and add a rule for tools_ssl_check: 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 Domainee. Nothing to install.
tools_ssl_check 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 tools_ssl_check 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 tools_ssl_check. 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.
tools_ssl_check is provided by the Domainee MCP server (https://mcp.domainee.dev/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Domainee, and thousands of servers like it.
This server
Across the catalogue