AI agents invoke ssh_session_start 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.
SSH session creation is fundamentally an Execute action—it initiates remote command execution whose effects depend entirely on arguments and attacker intent. On a Kali-focused MCP server alongside privilege escalation tools (psexec, wmiexec, secretsdump, kerberoast), this tool poses critical risk: an AI agent could use it to establish persistence, pivot through networks, exfiltrate data, or launch further attacks.
From the tool's definition Tool named 'ssh_session_start' on Kali Linux penetration testing toolkit server that grants AI agents direct access to comprehensive attack tools. The name explicitly indicates shell session initiation.
Documented attack patterns abuse exactly the kind of access ssh_session_start 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 ssh_session_start:
{
"version": "1",
"default": "deny",
"tools": {
"ssh_session_start": {
"limits": [
{
"counter": "ssh_session_start_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}ssh_session_start 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.
ssh_session_start. 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 ssh_session_start: 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.
ssh_session_start 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 ssh_session_start 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 ssh_session_start. 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.
ssh_session_start 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.