This record as markdown: /tools/io-github-kivanccakmak-yaver/acl-list-peer-tools.md
What acl_list_peer_tools does on Yaver
AI agents call acl_list_peer_tools 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.
| Parameter | Type | Required | Description |
|---|---|---|---|
peer_id | string | Yes | Peer ID |
Parameters from the server's own tool schema.
Why acl_list_peer_tools is rated Low
This is a straightforward informational query that discovers what capabilities are exposed by peer MCP servers. It has no destructive, financial, or code-execution implications. The read operation is limited to inspecting tool availability and metadata, making it a low-severity Read action.
From the tool's definition The tool name 'acl_list_peer_tools' and description 'List all tools available from a connected MCP peer' indicate a query/retrieval operation with no side effects. It retrieves metadata about available tools without modifying, executing, or deleting anything.
Attacks that exploit this kind of access
The rule that runs acl_list_peer_tools 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_list_peer_tools, this is the rule to start with:
acl_list_peer_tools is read-only, so it stays allowed. 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_list_peer_tools call is checked against it from then on.
Questions about acl_list_peer_tools
List all tools available from a connected MCP peer. It is categorised as a Read tool in the Yaver MCP Server, which means it retrieves data without modifying state.
acl_list_peer_tools 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_list_peer_tools: 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_list_peer_tools is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the acl_list_peer_tools 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_list_peer_tools. 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_list_peer_tools 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