beacon_list_directory

List directory contents on a beacon

SERVERCobalt Strike MCP Server SOURCEmickeydb/cobalt-strike-mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/mickeydb-cobalt-strike-mcp/beacon-list-directory.md

WHAT IT DOES

What beacon_list_directory does on Cobalt Strike MCP Server

AI agents call beacon_list_directory to retrieve information from Cobalt Strike MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why beacon_list_directory is rated Low

The tool queries and retrieves directory contents from a compromised host (beacon) without modifying, deleting, or executing operations. This is a Read operation. Severity is high because it provides reconnaissance data during active red team operations against a target system, enabling adversaries to map the filesystem and plan further attacks.

From the tool's definition Tool name 'beacon_list_directory' and description 'List directory contents on a beacon' indicate retrieval of directory listing with no side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

beacon_list_directory Allowed

beacon_list_directory is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "beacon_list_directory": {}
  }
}

ALLOW ONLY 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_list_directory call is checked against it from then on.

FAQ

Questions about beacon_list_directory

What does the beacon_list_directory tool do? +

List directory contents on a beacon. It is categorised as a Read tool in the Cobalt Strike MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on beacon_list_directory? +

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

beacon_list_directory is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit beacon_list_directory? +

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

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

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

KEEP EXPLORING

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

This server

All 220 Cobalt Strike MCP Server tools →

Across the catalogue

aiva_list_affiliates on AIVA MCP Server →list_circuits on 0gzk →list_agents on 0rca Dojo MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →