tunnel_test

Test connectivity to configured Cloudflare Tunnels (or a specific URL).

SERVERYaver SOURCEyaver-cli

Low RISK CLASS

Category Read

Parameters 10 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-test.md

WHAT IT DOES

What tunnel_test does on Yaver

AI agents call tunnel_test 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
`url`	string	—	Optional: specific tunnel URL to test. If omitted, tests all configured tunnels.

Parameters from the server's own tool schema.

RISK

Why tunnel_test is rated Low

A connectivity test is a read-only operation that queries network reachability. It has no side effects, does not modify data, and does not execute code. The blast radius of misuse is minimal — at worst it generates network traffic to a URL.

From the tool's definition 'Test connectivity to configured Cloudflare Tunnels (or a specific URL)' — this is a diagnostic/read operation that checks connectivity status without modifying anything.

Risk signalsAccepts URL/endpoint input (url)

Attacks that exploit this kind of access

RECOMMENDED RULE

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

tunnel_test Allowed

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

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

FAQ

Questions about tunnel_test

What does the tunnel_test tool do? +

Test connectivity to configured Cloudflare Tunnels (or a specific URL). It is categorised as a Read tool in the Yaver MCP Server, which means it retrieves data without modifying state.

What parameters does tunnel_test accept? +

tunnel_test accepts 1 parameter: url. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on tunnel_test? +

Register the Yaver MCP server in PolicyLayer and add a rule for tunnel_test: 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_test? +

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

Can I rate-limit tunnel_test? +

Yes. Add a rate_limit block to the tunnel_test 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_test completely? +

Set action: deny in the PolicyLayer policy for tunnel_test. 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_test? +

tunnel_test 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

The MCP Attack Database →

Guides

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