ssl_check
Check SSL/TLS certificate for a domain — expiry, issuer, SANs.
This record as markdown: /tools/io-github-kivanccakmak-yaver/ssl-check.md
What ssl_check does on Yaver
AI agents call ssl_check to retrieve information from Yaver 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 | Domain to check (e.g. yaver.io) |
Parameters from the server's own tool schema.
Why ssl_check is rated Low
This is a read-only information retrieval operation. It queries publicly available SSL certificate data without side effects. The blast radius of misuse is minimal—an attacker could enumerate certificate details to inform reconnaissance, but cannot modify infrastructure, execute commands, or cause direct harm.
From the tool's definition Tool performs a passive check of SSL/TLS certificate metadata (expiry, issuer, SANs) for a domain. The description uses verbs like 'check' and 'retrieve' certificate properties, with no indication of modification, deletion, code execution, or financial impact.
Risk signalsAccepts URL/endpoint input (host)
Attacks that exploit this kind of access
The rule that runs ssl_check safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Yaver, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For ssl_check, this is the rule to start with:
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 Yaver, apply this rule, and every ssl_check call is checked against it from then on.
Questions about ssl_check
Check SSL/TLS certificate for a domain — expiry, issuer, SANs. It is categorised as a Read tool in the Yaver MCP Server, which means it retrieves data without modifying state.
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 Yaver MCP server in PolicyLayer and add a rule for 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 Yaver. Nothing to install.
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 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 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.
ssl_check is provided by the Yaver MCP server (yaver-cli). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Yaver, and thousands of servers like it.
This server
Across the catalogue