New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

domain_setup

Full domain setup wizard — detects IP type, guides DNS, configures SSL.

SERVERYaver SOURCEyaver-cli
High RISK CLASS
Category Execute
Parameters 21 required
Recommended Rate-limitedsee the rule below
Registry record Grade F, identity unverified Pull the record →

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.

ParameterTypeRequiredDescription
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'

Questions about domain_setup

What does the domain_setup tool do? +

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.

What parameters does domain_setup accept? +

domain_setup accepts 2 parameters: domain, provider. Required: domain. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on domain_setup? +

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.

What risk level is domain_setup? +

domain_setup is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit domain_setup? +

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.

How do I block domain_setup completely? +

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.

What MCP server provides domain_setup? +

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.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Yaver's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.