stop_tunnel

Stop a managed local tunnel.

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

High RISK CLASS

Category Execute

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/mcp-control-plane/stop-tunnel.md

WHAT IT DOES

What stop_tunnel does on Mcp Control Plane

AI agents invoke stop_tunnel to trigger actions in Mcp Control Plane. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.

RISK

Why stop_tunnel is rated High

Stopping a tunnel is an Execute-class action because it triggers an external operation (tunnel termination) whose effects depend on which tunnel is targeted via arguments. It is not Destructive because tunnel shutdown is reversible (the tunnel can be restarted). It is not Write because it doesn't create or modify data reversibly—it stops a running service.

From the tool's definition Tool name 'stop_tunnel' and description 'Stop a managed local tunnel' indicates an action that terminates an active network tunnel, which is an operational change with external effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

stop_tunnel Rate-limited

stop_tunnel stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "stop_tunnel": {
      "limits": [
        {
          "counter": "stop_tunnel_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

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

FAQ

Questions about stop_tunnel

What does the stop_tunnel tool do? +

Stop a managed local tunnel. It is categorised as a Execute tool in the Mcp Control Plane MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on stop_tunnel? +

Register the Mcp Control Plane MCP server in PolicyLayer and add a rule for stop_tunnel: 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 stop_tunnel? +

stop_tunnel is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit stop_tunnel? +

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

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

stop_tunnel 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 → High-risk tools on this server →

Across the catalogue

stop_emba_scan on EMBA-MCP → All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →