ssl_provision
Provision a Let's Encrypt certificate for a domain via the installed certbot (http-01 challenge, standalone mode). Used on self-hosted yaver boxes that terminate TLS themselves. The yaver-managed-cloud SKU does this automatically via the platform's traefik; this MCP exists for BYO-host users. Own...
This record as markdown: /tools/io-github-kivanccakmak-yaver/ssl-provision.md
What ssl_provision does on Yaver
AI agents invoke ssl_provision to trigger actions in Yaver. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
| Parameter | Type | Required | Description |
|---|---|---|---|
email | string | Yes | ACME account email (Let's Encrypt notification address) |
domain | string | Yes | FQDN to issue a cert for (e.g. app.example.com) |
staging | boolean | — | Use Let's Encrypt staging endpoint (avoids rate limits during iteration) |
Parameters from the server's own tool schema.
Why ssl_provision is rated High
This tool executes an external system binary (certbot) on the host machine, triggering network operations (ACME http-01 challenge), certificate provisioning, and potentially modifying system TLS configuration. It is not merely a read or write operation — it actively runs a command-line tool and interacts with external infrastructure.
From the tool's definition 'Provision a Let's Encrypt certificate for a domain via the installed `certbot` (http-01 challenge, standalone mode)' — runs certbot as an external process on the host system
Attacks that exploit this kind of access
The rule that runs ssl_provision 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_provision, this is the rule to start with:
ssl_provision stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. 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_provision call is checked against it from then on.
Questions about ssl_provision
Provision a Let's Encrypt certificate for a domain via the installed certbot (http-01 challenge, standalone mode). Used on self-hosted yaver boxes that terminate TLS themselves. The yaver-managed-cloud SKU does this automatically via the platform's traefik; this MCP exists for BYO-host users. Owner-only; requires certbot present on PATH. It is categorised as a Execute tool in the Yaver MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
ssl_provision accepts 3 parameters: email, domain, staging. Required: email, domain. 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_provision: 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_provision is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the ssl_provision 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_provision. 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_provision 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.
Across the catalogue