proxychains_run
AI agents invoke proxychains_run to trigger actions in Kali Linux MCP Server. 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.
Proxychains enables routing network traffic through proxy chains, typically used to mask or route attack traffic. On a Kali pentesting server, 'proxychains_run' almost certainly executes arbitrary commands through proxy chains, affecting external systems and network behavior. This is Execute-class (triggers external operations with argument-dependent effects) rather than mere routing configuration.
From the tool's definition Tool named 'proxychains_run' with empty description on a Kali Linux penetration testing server alongside exploitation frameworks (beef_start, crackmapexec_scan) and attack tools (aircrack_attack, bully_attack).
Attacks that exploit this kind of access
proxychains_run. It is categorised as a Execute tool in the Kali Linux MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Kali Linux MCP Server MCP server in PolicyLayer and add a rule for proxychains_run: 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 Linux MCP Server. Nothing to install.
proxychains_run 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 proxychains_run 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 proxychains_run. 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.
proxychains_run is provided by the Kali Linux MCP Server MCP server (ofryma/custom-mcp-library). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →