This record as markdown: /tools/io-github-kivanccakmak-yaver/add-relay-server.md
What add_relay_server does on Yaver
AI agents use add_relay_server 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 |
|---|---|---|---|
label | string | — | Human-friendly label |
http_url | string | — | HTTP proxy URL |
password | string | — | Relay password |
quic_addr | string | Yes | QUIC address (host:port) |
Parameters from the server's own tool schema.
Why add_relay_server is rated Medium
The tool creates a new relay server entry for NAT traversal, which is a reversible Write operation (the entry can be removed/modified later). It modifies application infrastructure configuration but does not execute arbitrary code, delete data, or move financial assets.
From the tool's definition Tool description states 'Add a relay server' — this creates/adds a new network configuration resource that did not previously exist.
Risk signalsHandles credentials or secrets (password)
Attacks that exploit this kind of access
The rule that runs add_relay_server 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 add_relay_server, this is the rule to start with:
add_relay_server 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 add_relay_server call is checked against it from then on.
Questions about add_relay_server
Add a relay server for NAT traversal. 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.
add_relay_server accepts 4 parameters: label, http_url, password, quic_addr. Required: quic_addr. 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 add_relay_server: 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.
add_relay_server 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 add_relay_server 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 add_relay_server. 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.
add_relay_server 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