beacon_copy_file

Copy a file on a beacon

SERVERCobalt Strike MCP Server SOURCEmickeydb/cobalt-strike-mcp

High RISK CLASS

Category Execute

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-copy-file.md

WHAT IT DOES

What beacon_copy_file does on Cobalt Strike MCP Server

AI agents invoke beacon_copy_file 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.

RISK

Why beacon_copy_file is rated High

This tool executes a file copy operation on a remote beacon (a compromised system in a red team/adversary simulation context). While copying a file is not inherently destructive, executing commands on a remote beacon has significant blast radius: it can be used to stage payloads, duplicate sensitive files for exfiltration, or overwrite existing files.

From the tool's definition 'Copy a file on a beacon' — executes a file copy operation on a remote Cobalt Strike beacon (compromised host)

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs beacon_copy_file 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_copy_file, this is the rule to start with:

beacon_copy_file Rate-limited

beacon_copy_file 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": {
    "beacon_copy_file": {
      "limits": [
        {
          "counter": "beacon_copy_file_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Cobalt Strike MCP Server, apply this rule, and every beacon_copy_file call is checked against it from then on.

FAQ

Questions about beacon_copy_file

What does the beacon_copy_file tool do? +

Copy a file on a beacon. 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 beacon_copy_file? +

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

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

Can I rate-limit beacon_copy_file? +

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

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

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

KEEP EXPLORING

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

This server

All 220 Cobalt Strike MCP Server tools → High-risk tools on this server →

Across the catalogue

All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →