set_killdate · Cobalt Strike MCP Server MCP: Risk & Policy

WHAT IT DOES

What set_killdate does on Cobalt Strike MCP Server

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

WHY IT NEEDS A POLICY

Why set_killdate needs a policy

Setting a kill date modifies the configuration of a Cobalt Strike beacon or payload, determining when it will cease operating. This is a Write operation (reversible configuration change) rather than Destructive, but carries high severity because it controls the operational lifespan of an implant in a red team (or potentially malicious) context.

From the tool's definition 'Set kill date' — configures a kill date parameter on a beacon or payload

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

set_killdate Rate-limited

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

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "set_killdate": {
      "limits": [
        {
          "counter": "set_killdate_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

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 set_killdate

What does the set_killdate tool do? +

Set kill date. It is categorised as a Write tool in the Cobalt Strike MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on set_killdate? +

Register the Cobalt Strike MCP Server MCP server in PolicyLayer and add a rule for set_killdate: 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 set_killdate? +

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

Can I rate-limit set_killdate? +

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

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

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