whoisjson.ssl.check
Validate SSL/TLS certificate for any domain. Returns issuer (org, CN), validity dates, subject CN, wildcard status, key size, and Subject Alternative Names (SAN) list. Useful for security audits, monitoring cert expiration, and verifying HTTPS configuration (WhoisJSON)
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/whoisjson.ssl.check.md
What whoisjson.ssl.check does on Apibase
AI agents call whoisjson.ssl.check to retrieve information from Apibase 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 |
|---|---|---|---|
domain | string | Yes | Domain name to check SSL certificate (e.g. google.com, apibase.pro) |
Parameters from the server's own tool schema.
Why whoisjson.ssl.check is rated Low
Reads and retrieves SSL certificate metadata for a domain with no side effects or modifications.
From the tool's definition Validate SSL/TLS certificate, returns issuer, validity dates, subject CN, wildcard status, key size, SAN list
Attacks that exploit this kind of access
The rule that runs whoisjson.ssl.check safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Apibase, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For whoisjson.ssl.check, this is the rule to start with:
whoisjson.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 Apibase, apply this rule, and every whoisjson.ssl.check call is checked against it from then on.
Questions about whoisjson.ssl.check
Validate SSL/TLS certificate for any domain. Returns issuer (org, CN), validity dates, subject CN, wildcard status, key size, and Subject Alternative Names (SAN) list. Useful for security audits, monitoring cert expiration, and verifying HTTPS configuration (WhoisJSON). It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
whoisjson.ssl.check accepts 1 parameter: domain. Required: domain. The full parameter table on this page comes from the server's own tool schema.
Register the Apibase MCP server in PolicyLayer and add a rule for whoisjson.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 Apibase. Nothing to install.
whoisjson.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 whoisjson.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 whoisjson.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.
whoisjson.ssl.check is provided by the Apibase MCP server (apibase-mcp-client). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Apibase, and thousands of servers like it.
This server
Across the catalogue