add_relay_server · Yaver MCP: Risk & Policy

WHAT IT DOES

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.

PARAMETERS

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 IT NEEDS A POLICY

Why add_relay_server needs a policy

An AI agent can call add_relay_server faster than any human can review — one bad instruction and it creates or modifies resources in Yaver by the hundred, each call as confident as the last.

Risk signalsHandles credentials or secrets (password)

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

add_relay_server Rate-limited

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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "add_relay_server": {
      "limits": [
        {
          "counter": "add_relay_server_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Yaver, so you can run agents against it safely.

FAQ

Questions about add_relay_server

What does the add_relay_server tool do? +

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.

What parameters does add_relay_server accept? +

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.

How do I enforce a policy on add_relay_server? +

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.

What risk level is add_relay_server? +

add_relay_server is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit add_relay_server? +

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.

How do I block add_relay_server completely? +

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.

What MCP server provides add_relay_server? +

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.