execute_kill_process · Cobalt Strike MCP Server MCP

WHAT IT DOES

What execute_kill_process does on Cobalt Strike MCP Server

AI agents invoke execute_kill_process to trigger actions in Cobalt Strike 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.

WHY IT NEEDS A POLICY

Why execute_kill_process needs a policy

This tool executes an irreversible action (process termination) on a target system via beacon control. While process termination could be considered destructive in some contexts, it is classified as Execute because: (1) the primary function is to trigger an external operation (process kill) whose effects depend on the PID argument, (2) it represents active code execution on a remote system, (3) in the red team…

From the tool's definition Tool name 'execute_kill_process' and description 'Kill a process by PID' indicate termination of running processes.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

execute_kill_process Rate-limited

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

View as policy code

policy.json

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

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Cobalt Strike MCP Server, so you can run agents against it safely.

FAQ

Questions about execute_kill_process

What does the execute_kill_process tool do? +

Kill a process by PID. It is categorised as a Execute tool in the Cobalt Strike MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on execute_kill_process? +

Register the Cobalt Strike MCP Server MCP server in PolicyLayer and add a rule for execute_kill_process: 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 Cobalt Strike MCP Server. Nothing to install.

What risk level is execute_kill_process? +

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

Can I rate-limit execute_kill_process? +

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

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

execute_kill_process is provided by the Cobalt Strike MCP Server MCP server (mickeydb/cobalt-strike-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.