This record as markdown: /tools/io-github-kivanccakmak-yaver/acl-remove-peer.md
What acl_remove_peer does on Yaver
AI agents call acl_remove_peer to permanently remove resources in Yaver, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
| Parameter | Type | Required | Description |
|---|---|---|---|
peer_id | string | Yes | Peer ID to remove |
Parameters from the server's own tool schema.
Why acl_remove_peer is rated Critical
Removing a peer from an ACL or disconnecting it is a destructive operation: it revokes access or severs a connection in a way that requires explicit re-establishment. The 'remove' in the tool name and 'disconnect' in the description both indicate an irreversible deletion of a relationship/configuration, placing this in the Destructive category with high severity given it could cut off critical peer connections.
From the tool's definition 'Disconnect from an MCP peer' and 'acl_remove_peer' — removing/disconnecting a peer implies an irreversible removal of an access control list entry or peer connection that cannot be automatically undone.
Attacks that exploit this kind of access
The rule that runs acl_remove_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_remove_peer, this is the rule to start with:
acl_remove_peer is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Yaver, apply this rule, and every acl_remove_peer call is checked against it from then on.
Questions about acl_remove_peer
Disconnect from an MCP peer. It is categorised as a Destructive tool in the Yaver MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
acl_remove_peer accepts 1 parameter: peer_id. Required: peer_id. 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_remove_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_remove_peer is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the acl_remove_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_remove_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_remove_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