New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

beacon_create_directory

Create a directory on a beacon

SERVERCobalt Strike MCP Server SOURCEmickeydb/cobalt-strike-mcp
Medium RISK CLASS
Category Write
Parameters 00 required
Recommended Rate-limitedsee the rule below
Registry record Grade F, identity unverified Pull the record →

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.

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.

More on Cobalt Strike MCP Server, and thousands of servers like it.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Cobalt Strike MCP Server's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.