This record as markdown: /tools/io-github-kivanccakmak-yaver/expose-list.md
What expose_list does on Yaver
AI agents call expose_list 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.
Why expose_list is rated Low
This tool retrieves information about active tunnels and their public URLs. While it performs no modifications or deletions, the exposure of tunnel URLs and their active status could reveal infrastructure details and development endpoints to an unauthorized user, warranting medium severity. However, it remains fundamentally a Read operation as it queries and returns existing state without side effects.
From the tool's definition Tool name 'expose_list' and description 'List active tunnels with their public URLs' indicate a query/retrieval operation. The word 'List' denotes read-only enumeration without data modification.
Attacks that exploit this kind of access
The rule that runs expose_list 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 expose_list, this is the rule to start with:
expose_list 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 expose_list call is checked against it from then on.
Questions about expose_list
List active tunnels with their public URLs. It is categorised as a Read tool in the Yaver MCP Server, which means it retrieves data without modifying state.
Register the Yaver MCP server in PolicyLayer and add a rule for expose_list: 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.
expose_list 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 expose_list 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 expose_list. 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.
expose_list 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