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

start_ssh_tunnel

A execute tool on the Pentester- MCP server.

SERVERPentester-MCP SOURCEhalilkirazkaya/pentester-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/halilkirazkaya-pentester-mcp/start-ssh-tunnel.md

What start_ssh_tunnel does on Pentester-MCP

AI agents invoke start_ssh_tunnel to trigger actions in Pentester-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 start_ssh_tunnel is rated High

SSH tunnel creation is an Execute action—it runs a command/process to establish network connections and modify traffic flow. While not inherently destructive or financial, it enables arbitrary network operations whose impact depends on what the tunnel is used for. In a penetration testing context with 200+ exploitation tools, starting tunnels could facilitate unauthorized access or lateral movement.

From the tool's definition Tool named 'start_ssh_tunnel' with empty description; context indicates this MCP server enables execution of penetration testing tools.

Questions about start_ssh_tunnel

What does the start_ssh_tunnel tool do? +

start_ssh_tunnel is a execute tool on the Pentester MCP server. It is categorised as a Execute tool in the Pentester-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 start_ssh_tunnel? +

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

What risk level is start_ssh_tunnel? +

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

Can I rate-limit start_ssh_tunnel? +

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

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

start_ssh_tunnel is provided by the Pentester MCP server (halilkirazkaya/pentester-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

More on Pentester, 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 Pentester'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.