AI agents invoke pivot_ssh_dynamic 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.
Creating a dynamic SOCKS proxy via SSH is an active network operation that establishes a persistent tunnel, enabling traffic to be routed through compromised hosts. In the context of a Kali Linux penetration testing toolkit, this is a pivoting technique used to access otherwise unreachable network segments. It executes an external SSH process and modifies network routing behavior.
From the tool's definition 'Create an SSH dynamic SOCKS proxy' — establishes an active SSH tunnel/proxy that routes network traffic through a remote host, enabling lateral movement and network pivoting
Documented attack patterns abuse exactly the kind of access pivot_ssh_dynamic gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Zebbern Kali MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for pivot_ssh_dynamic:
{
"version": "1",
"default": "deny",
"tools": {
"pivot_ssh_dynamic": {
"limits": [
{
"counter": "pivot_ssh_dynamic_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}pivot_ssh_dynamic 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.
Free to start. No card required.
Create an SSH dynamic SOCKS proxy. 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.
Register the Zebbern Kali MCP server in PolicyLayer and add a rule for pivot_ssh_dynamic: 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.
pivot_ssh_dynamic is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the pivot_ssh_dynamic 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 pivot_ssh_dynamic. 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.
pivot_ssh_dynamic 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.
Deterministic rules across all 128 Zebbern Kali MCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
128 Zebbern Kali MCP tools catalogued and risk-classified — across an index of 42,500+ MCP servers.