Medium Risk

exploit_copy

Copy an exploit to a working directory for modification.

How to control exploit_copy ↓

AI agents use exploit_copy to create or update resources in Zebbern Kali MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Zebbern Kali MCP environment.

Medium Risk

This tool copies exploit code to a writable location, enabling modification and execution. While it doesn't directly execute code, it prepares exploits for use and is part of a penetration testing toolkit (Kali Linux). The severity is high because copied and modified exploits could be used to compromise systems, though the tool itself only performs the non-destructive action of copying.

From the tool's definition Tool description states 'Copy an exploit to a working directory for modification.' The verb 'copy' and 'for modification' indicate the tool creates or stages data (exploit code) in a working directory, which is a write operation.

Documented attack patterns abuse exactly the kind of access exploit_copy 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 exploit_copy:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "exploit_copy": {
      "limits": [
        {
          "counter": "exploit_copy_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

exploit_copy stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Zebbern Kali MCP — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
LIMIT THIS TOOL →

Free to start. No card required.

Go deeper

What does the exploit_copy tool do? +

Copy an exploit to a working directory for modification. It is categorised as a Write tool in the Zebbern Kali MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on exploit_copy? +

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

What risk level is exploit_copy? +

exploit_copy is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit exploit_copy? +

Yes. Add a rate_limit block to the exploit_copy 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 exploit_copy completely? +

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

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

Enforce policy on every Zebbern Kali MCP tool call.

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.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.