List all active reverse-shell connections.
AI agents call shell_connection_list to retrieve information from Kali-Mcp-Toolkit without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves information about existing reverse-shell connections without creating, modifying, or deleting them. While it is purely a read operation, the severity is high because the information exposed (active reverse-shell connections) is sensitive in a penetration testing context and could reveal critical infrastructure details if misused by a malicious AI agent or attacker.
From the tool's definition Tool description states it 'List[s] all active reverse-shell connections' — a read-only operation that queries state without modifying it.
Documented attack patterns abuse exactly the kind of access shell_connection_list gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Kali-Mcp-Toolkit, and nothing reaches the server without passing your rules. This is the rule we recommend for shell_connection_list:
{
"version": "1",
"default": "deny",
"tools": {
"shell_connection_list": {}
}
} shell_connection_list is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
List all active reverse-shell connections. It is categorised as a Read tool in the Kali-Mcp-Toolkit MCP Server, which means it retrieves data without modifying state.
Register the Kali-Mcp-Toolkit MCP server in PolicyLayer and add a rule for shell_connection_list: 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 Kali-Mcp-Toolkit. Nothing to install.
shell_connection_list is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the shell_connection_list 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 shell_connection_list. 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.
shell_connection_list is provided by the Kali-Mcp-Toolkit MCP server (trymonoly/kali-mcp-toolkit). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Kali-Mcp-Toolkit, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
20 Kali-Mcp-Toolkit tools catalogued and risk-classified — across an index of 43,000+ MCP servers.