code_install_deps

THE RISK

High Risk

Why code_install_deps needs a policy

Installing packages executes privileged system-level operations (e.g., apt-get install) that modify the system environment. This goes beyond a simple write as it triggers external package manager execution with admin/root scope. On a Kali Linux penetration testing server, this could be misused to install malicious tools or alter the security posture of the system.

From the tool's definition 'Install packages (requires admin scope, must be enabled in config)' — installing packages modifies system state by running package manager commands with elevated privileges

Risk signalsAdmin/system-level operation

Documented attack patterns abuse exactly the kind of access code_install_deps gives an agent:

POLICY

How to control code_install_deps

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 code_install_deps:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "code_install_deps": {
      "limits": [
        {
          "counter": "code_install_deps_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

code_install_deps 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.

Create a free account and register Kali-Mcp-Toolkit — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

RATE-LIMIT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Kali-Mcp-Toolkit tools

Destructive terminal_kill Destroy a terminal session and free resources. Execute code_execute Execute a script/program from the workspace. Execute shell_connection_exec Execute a command on a reverse-shell connection and return output. Execute shell_listener_start Start a reverse-shell listener (requires admin scope, must be enabled in config). Execute shell_listener_stop Stop a reverse-shell listener. Execute terminal_exec Execute a command in an existing terminal session. Execute exec_tool exec_tool Execute terminal_create Create a new interactive PTY terminal session.

All 20 Kali-Mcp-Toolkit tools →

Execute tools on other servers

Android Forensics ADB MCP Server adb_shell_command EMBA-MCP run_emba_scan Frida Game Hacking MCP remove_breakpoint Procmon request_elevation

Go deeper

High-risk tools in Kali-Mcp-Toolkit → Every high-risk tool this server exposes, in one view.
All high-risk MCP tools → Every high-risk tool across the catalogue, and the policy pattern that contains them.
The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Agent sandbox → Bounding what an agent can execute and where the boundary should sit.
Least privilege for MCP → Granting agents the minimum tool surface the task needs.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about code_install_deps

What does the code_install_deps tool do? +

Install packages (requires admin scope, must be enabled in config). It is categorised as a Execute tool in the Kali-Mcp-Toolkit MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on code_install_deps? +

Register the Kali-Mcp-Toolkit MCP server in PolicyLayer and add a rule for code_install_deps: 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.

What risk level is code_install_deps? +

code_install_deps is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit code_install_deps? +

Yes. Add a rate_limit block to the code_install_deps 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.

How do I block code_install_deps completely? +

Set action: deny in the PolicyLayer policy for code_install_deps. 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.

What MCP server provides code_install_deps? +

code_install_deps 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.

Enforce policy on every Kali-Mcp-Toolkit tool call.

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.

CHECK YOUR STACK →