This record as markdown: /tools/io-github-kivanccakmak-yaver/domain-add.md
What domain_add does on Yaver
AI agents use domain_add to create or update resources in Yaver, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Yaver environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
path | string | — | Path prefix (default: /) |
domain | string | Yes | |
target | string | Yes | App name or port |
Parameters from the server's own tool schema.
Why domain_add is rated Medium
This tool creates or registers a new domain routing entry, which modifies application configuration persistibly. It is categorized as Write (creates/modifies data reversibly) rather than Execute because it configures infrastructure rather than triggering runtime operations.
From the tool's definition Tool name 'domain_add' and description 'Add domain routing (map domain to an app or port)' indicate creation of a new domain mapping configuration.
Risk signalsAccepts file system path (path)
Attacks that exploit this kind of access
The rule that runs domain_add 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_add, this is the rule to start with:
domain_add stays usable, but capped: an agent stuck in a loop can't make hundreds of changes 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_add call is checked against it from then on.
Questions about domain_add
Add domain routing (map domain to an app or port). It is categorised as a Write tool in the Yaver MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
domain_add accepts 3 parameters: path, domain, target. Required: domain, target. 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_add: 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_add is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the domain_add 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_add. 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_add 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