This record as markdown: /tools/seac-25-kali-security-mcp/ws-connect.md
What ws_connect does on Kali Security MCP
AI agents invoke ws_connect to trigger actions in Kali Security 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 ws_connect is rated High
This tool establishes a WebSocket connection to an external target. On a penetration-testing server with tools like adaptive_web_penetration and adaptive_cmdi_test, initiating WebSocket connections can be used to probe, exploit, or tunnel data through target systems. It is an active operation with external side effects (network connection), placing it in Execute.
From the tool's definition 建立WebSocket连接 (Establish WebSocket connection) — actively initiates a network connection to an external endpoint
Attacks that exploit this kind of access
The rule that runs ws_connect safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Kali Security MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For ws_connect, this is the rule to start with:
ws_connect 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Kali Security MCP, apply this rule, and every ws_connect call is checked against it from then on.
Questions about ws_connect
建立WebSocket连接. It is categorised as a Execute tool in the Kali Security MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Kali Security MCP server in PolicyLayer and add a rule for ws_connect: 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 Security MCP. Nothing to install.
ws_connect 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 ws_connect 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 ws_connect. 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.
ws_connect is provided by the Kali Security MCP server (seac-25/kali-security-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Kali Security, and thousands of servers like it.
Across the catalogue