tunnel_status

Return status for a local tunnel.

SERVERMcp Control Plane SOURCEalbertik322-sudo/mcp-control-plane

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/mcp-control-plane/tunnel-status.md

WHAT IT DOES

What tunnel_status does on Mcp Control Plane

AI agents call tunnel_status to retrieve information from Mcp Control Plane 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_status is rated Low

This tool retrieves and returns status data about an existing tunnel—a straightforward read operation. No data is created, modified, deleted, or executed. The blast radius if misused is minimal: an agent could only gain visibility into tunnel states, not cause infrastructure changes or disruptions.

From the tool's definition Tool name 'tunnel_status' and description 'Return status for a local tunnel' indicate a read-only query operation that retrieves status information without modification or side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs tunnel_status safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Mcp Control Plane, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For tunnel_status, this is the rule to start with:

tunnel_status Allowed

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

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Mcp Control Plane, apply this rule, and every tunnel_status call is checked against it from then on.

FAQ

Questions about tunnel_status

What does the tunnel_status tool do? +

Return status for a local tunnel. It is categorised as a Read tool in the Mcp Control Plane MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on tunnel_status? +

Register the Mcp Control Plane MCP server in PolicyLayer and add a rule for tunnel_status: 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 Control Plane. Nothing to install.

What risk level is tunnel_status? +

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

Can I rate-limit tunnel_status? +

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

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

tunnel_status is provided by the Mcp Control Plane MCP server (albertik322-sudo/mcp-control-plane). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Mcp Control Plane, and thousands of servers like it.

This server

All 286 Mcp Control Plane tools →

Across the catalogue

claude_git_status on Claude Bridge →get_task_status on 0rca Dojo MCP Server → The MCP Attack Database →

Guides

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