tunnel_list

List configured Cloudflare Tunnels.

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/tunnel-list.md

WHAT IT DOES

What tunnel_list does on Yaver

AI agents call tunnel_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.

RISK

Why tunnel_list is rated Low

This tool retrieves information about configured tunnels—a read-only operation with no side effects. It does not create, modify, delete, or execute any actions. The blast radius of misuse is minimal; an attacker gaining access would only be able to enumerate tunnel configurations, not alter infrastructure or move data.

From the tool's definition Tool name 'tunnel_list' and description 'List configured Cloudflare Tunnels' indicate a query operation that retrieves and displays existing tunnel configurations without modifying or deleting them.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

tunnel_list Allowed

tunnel_list 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": {
    "tunnel_list": {}
  }
}

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 tunnel_list call is checked against it from then on.

FAQ

Questions about tunnel_list

What does the tunnel_list tool do? +

List configured Cloudflare Tunnels. 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 tunnel_list? +

Register the Yaver MCP server in PolicyLayer and add a rule for tunnel_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.

What risk level is tunnel_list? +

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

Can I rate-limit tunnel_list? +

Yes. Add a rate_limit block to the tunnel_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.

How do I block tunnel_list completely? +

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

What MCP server provides tunnel_list? +

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

KEEP EXPLORING

More on Yaver, and thousands of servers like it.

This server

All 645 Yaver tools →

Across the catalogue

aiva_list_affiliates on AIVA MCP Server →list_agents on 0rca Dojo MCP Server → The MCP Attack Database →

Guides

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