This record as markdown: /tools/io-github-kivanccakmak-yaver/acl-add-peer.md
What acl_add_peer does on Yaver
AI agents invoke acl_add_peer 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.
| Parameter | Type | Required | Description |
|---|---|---|---|
url | string | Yes | MCP endpoint URL |
auth | string | — | Bearer token |
name | string | Yes | Peer name |
Parameters from the server's own tool schema.
Why acl_add_peer is rated High
This tool establishes a connection to an external MCP server, which is an external operation with effects that depend on the target server address/arguments. It doesn't merely read data — it initiates a network connection and integrates with potentially arbitrary remote services. This falls under Execute as it triggers external operations.
From the tool's definition Connect to another MCP server (local or remote)
Risk signalsAccepts URL/endpoint input (url) · Handles credentials or secrets (auth)
Attacks that exploit this kind of access
The rule that runs acl_add_peer 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 acl_add_peer, this is the rule to start with:
acl_add_peer stays usable, but rate-capped: a runaway agent can't fire it dozens of times 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 acl_add_peer call is checked against it from then on.
Questions about acl_add_peer
Connect to another MCP server (local or remote). 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.
acl_add_peer accepts 3 parameters: url, auth, name. Required: url, name. 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 acl_add_peer: 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.
acl_add_peer is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the acl_add_peer 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 acl_add_peer. 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.
acl_add_peer 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.
Across the catalogue