beacon_create_directory
Create a directory on a beacon
This record as markdown: /tools/mickeydb-cobalt-strike-mcp/beacon-create-directory.md
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 beacon_create_directory is rated Medium
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
The rule that runs beacon_create_directory safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Cobalt Strike MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For beacon_create_directory, this is the rule to start with:
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.
The button opens the PolicyLayer dashboard: create your workspace, connect Cobalt Strike MCP Server, apply this rule, and every beacon_create_directory call is checked against it from then on.
Questions about beacon_create_directory
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.
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.
beacon_create_directory is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
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.
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.
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.
More on Cobalt Strike MCP Server, and thousands of servers like it.
This server
Across the catalogue