This record as markdown: /tools/io-github-kivanccakmak-yaver/domain-ssl-status.md
What domain_ssl_status does on Yaver
AI agents call domain_ssl_status 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.
Why domain_ssl_status is rated Low
This tool retrieves and displays SSL certificate status information for domains. It performs no data modification, code execution, deletion, or financial operations. It is a read-only query operation with minimal blast radius if misused—an agent could only gather information about existing SSL certificates. No side effects are possible.
From the tool's definition Tool name 'domain_ssl_status' and description 'Show SSL certificate status for all domains' indicate a query/retrieval operation with no modification or execution of external operations.
Attacks that exploit this kind of access
The rule that runs domain_ssl_status 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 domain_ssl_status, this is the rule to start with:
domain_ssl_status 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 domain_ssl_status call is checked against it from then on.
Questions about domain_ssl_status
Show SSL certificate status for all domains. It is categorised as a Read tool in the Yaver MCP Server, which means it retrieves data without modifying state.
Register the Yaver MCP server in PolicyLayer and add a rule for domain_ssl_status: 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.
domain_ssl_status 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 domain_ssl_status 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 domain_ssl_status. 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.
domain_ssl_status 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