beacon_create_directory · Cobalt Strike MCP Server MCP

WHAT IT DOES

What beacon_create_directory does on Cobalt Strike MCP Server

AI agents use beacon_create_directory 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 beacon_create_directory needs a policy

The tool creates a new directory on a compromised system (beacon). While reversible (directories can be deleted), it modifies system state on a remote host. This is Write rather than Execute because it performs a specific file system operation without running arbitrary code.

From the tool's definition Tool name explicitly states 'beacon_create_directory' and description confirms it will 'Create a directory on a beacon' — a remote system under attacker control. This is a reversible file system modification operation.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

beacon_create_directory Rate-limited

beacon_create_directory 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": {
    "beacon_create_directory": {
      "limits": [
        {
          "counter": "beacon_create_directory_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 beacon_create_directory

What does the beacon_create_directory tool do? +

Create a directory on a beacon. 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 beacon_create_directory? +

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

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

Can I rate-limit beacon_create_directory? +

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

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

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