New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

pivot_stop_all_tunnels

Stop all active tunnels and port forwards.

SERVERZebbern Kali MCP SOURCEzebbern/zebbern-kali-mcp
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/zebbern-zebbern-kali-mcp/pivot-stop-all-tunnels.md

What pivot_stop_all_tunnels does on Zebbern Kali MCP

AI agents invoke pivot_stop_all_tunnels to trigger actions in Zebbern Kali MCP. 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.

Why pivot_stop_all_tunnels is rated High

This tool executes a command to stop tunnels and port forwards—an operational action triggered externally. While not destructive in the sense of deleting data, it terminates active network operations which can disrupt ongoing activities and depend on the state of the system.

From the tool's definition Tool name 'pivot_stop_all_tunnels' and description 'Stop all active tunnels and port forwards' indicate execution of commands that terminate network operations with system-wide effects.

Questions about pivot_stop_all_tunnels

What does the pivot_stop_all_tunnels tool do? +

Stop all active tunnels and port forwards. It is categorised as a Execute tool in the Zebbern Kali MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on pivot_stop_all_tunnels? +

Register the Zebbern Kali MCP server in PolicyLayer and add a rule for pivot_stop_all_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 Zebbern Kali MCP. Nothing to install.

What risk level is pivot_stop_all_tunnels? +

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

Can I rate-limit pivot_stop_all_tunnels? +

Yes. Add a rate_limit block to the pivot_stop_all_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.

How do I block pivot_stop_all_tunnels completely? +

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

What MCP server provides pivot_stop_all_tunnels? +

pivot_stop_all_tunnels is provided by the Zebbern Kali MCP server (zebbern/zebbern-kali-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

More on Zebbern Kali, and thousands of servers like it.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Zebbern Kali's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.