get_relay_config

List configured relay servers.

SERVERYaver SOURCEyaver-cli

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-kivanccakmak-yaver/get-relay-config.md

WHAT IT DOES

What get_relay_config does on Yaver

AI agents call get_relay_config to retrieve information from Yaver without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why get_relay_config is rated Low

This tool retrieves configuration information about relay servers. The verb 'list' and the retrieval nature of the operation with no side effects places it squarely in the Read category. The severity is low because configuration data exposure has limited impact in a local dev environment (Yaver is described as phone-first local dev MCP). No data is created, modified, deleted, or financial operations are involved.

From the tool's definition Tool name 'get_relay_config' with description 'List configured relay servers' indicates a retrieval operation with no modification.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs get_relay_config 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 get_relay_config, this is the rule to start with:

get_relay_config Allowed

get_relay_config is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_relay_config": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Yaver, apply this rule, and every get_relay_config call is checked against it from then on.

FAQ

Questions about get_relay_config

What does the get_relay_config tool do? +

List configured relay servers. It is categorised as a Read tool in the Yaver MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_relay_config? +

Register the Yaver MCP server in PolicyLayer and add a rule for get_relay_config: 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 get_relay_config? +

get_relay_config is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_relay_config? +

Yes. Add a rate_limit block to the get_relay_config 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 get_relay_config completely? +

Set action: deny in the PolicyLayer policy for get_relay_config. 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 get_relay_config? +

get_relay_config 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.

KEEP EXPLORING

More on Yaver, and thousands of servers like it.

This server

All 645 Yaver tools →

Across the catalogue

get_cocktail_by_category on Cocktails RAG MCP Server →get_torrent_detail on M-Team MCP Server →aiva_get_affiliate on AIVA MCP Server →get-chuck-categories on Jokes MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →