domain_setup
Full domain setup wizard — detects IP type, guides DNS, configures SSL.
This record as markdown: /tools/io-github-kivanccakmak-yaver/domain-setup.md
What domain_setup does on Yaver
AI agents invoke domain_setup 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 |
|---|---|---|---|
domain | string | Yes | |
provider | string | — | DNS provider: cloudflare, manual (default: manual) |
Parameters from the server's own tool schema.
Why domain_setup is rated High
This tool performs external operations including DNS configuration and SSL certificate setup, which are active system-level changes to network and security infrastructure. These operations trigger external side effects (DNS record changes, SSL provisioning) and are not simply reads or writes to a data store. Misconfiguration could expose services or cause outages, warranting high severity.
From the tool's definition 'Full domain setup wizard — detects IP type, guides DNS, configures SSL'
Attacks that exploit this kind of access
The rule that runs domain_setup 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_setup, this is the rule to start with:
domain_setup 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 domain_setup call is checked against it from then on.
Questions about domain_setup
Full domain setup wizard — detects IP type, guides DNS, configures SSL. 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.
domain_setup accepts 2 parameters: domain, provider. Required: 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 domain_setup: 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_setup 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 domain_setup 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_setup. 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_setup 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