Lists all active tunnels including their status and details. This tool will: - Show all tunnels in the registry - Auto-detect any running tunnels not in the registry - Display tunnel status, name, URLs, and runtime information - Indicate whether tunnels are local or running on remote machines Use...
AI agents call list_tunnels to retrieve information from Mcp Untun without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs query and information retrieval operations only. It reads the current state of tunnels (status, names, URLs, runtime information) and auto-detects running tunnels, but produces no side effects, modifications, deletions, or external operations. It is a classic Read operation with minimal blast radius if misused—an agent could only gather information about existing tunnel infrastructure.
From the tool's definition Tool description explicitly states it 'Lists all active tunnels' and 'Show all tunnels in the registry' with purposes of checking status and retrieving public URLs.
Attacks that exploit this kind of access
Lists all active tunnels including their status and details. This tool will: - Show all tunnels in the registry - Auto-detect any running tunnels not in the registry - Display tunnel status, name, URLs, and runtime information - Indicate whether tunnels are local or running on remote machines Use this tool to check the status of your tunnels and get their public URLs. It is categorised as a Read tool in the Mcp Untun MCP Server, which means it retrieves data without modifying state.
Register the Mcp Untun MCP server in PolicyLayer and add a rule for list_tunnels: 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 Mcp Untun. Nothing to install.
list_tunnels 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 list_tunnels 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 list_tunnels. 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.
list_tunnels is provided by the Mcp Untun MCP server (minte-app/untun-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →