This record as markdown: /tools/io-github-kivanccakmak-yaver/tunnel-add.md
What tunnel_add does on Yaver
AI agents use tunnel_add to create or update resources in Yaver, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Yaver environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
url | string | Yes | Tunnel URL (e.g. https://my-tunnel.example.com) |
label | string | — | Human-readable label (optional) |
cf_client_id | string | — | CF Access Service Token Client ID (optional) |
cf_client_secret | string | — | CF Access Service Token Client Secret (optional) |
Parameters from the server's own tool schema.
Why tunnel_add is rated Medium
This tool creates a new Cloudflare Tunnel endpoint, which is a Write operation (creates a new network resource). Misuse could expose internal services to the internet, giving it medium severity, but it is reversible (tunnels can be removed).
From the tool's definition Add a Cloudflare Tunnel endpoint for NAT traversal
Risk signalsAccepts URL/endpoint input (url)
Attacks that exploit this kind of access
The rule that runs tunnel_add 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_add, this is the rule to start with:
tunnel_add stays usable, but capped: an agent stuck in a loop can't make hundreds of changes 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 tunnel_add call is checked against it from then on.
Questions about tunnel_add
Add a Cloudflare Tunnel endpoint for NAT traversal. It is categorised as a Write tool in the Yaver MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
tunnel_add accepts 4 parameters: url, label, cf_client_id, cf_client_secret. Required: url. 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 tunnel_add: 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.
tunnel_add is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the tunnel_add 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 tunnel_add. 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.
tunnel_add 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