beacon_get_current_directory
Get current working directory on a beacon
This record as markdown: /tools/mickeydb-cobalt-strike-mcp/beacon-get-current-directory.md
What beacon_get_current_directory does on Cobalt Strike MCP Server
AI agents call beacon_get_current_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.
Why beacon_get_current_directory is rated Low
This tool queries state (current directory path) from a compromised/controlled host (beacon) with no side effects. It is a Read operation. However, severity is high because the Cobalt Strike context indicates this is a red team/adversarial tool operating on hosts already compromised by an attacker framework.
From the tool's definition beacon_get_current_directory retrieves the current working directory on a beacon without modifying system state. The description uses 'Get', a read-only operation.
Attacks that exploit this kind of access
The rule that runs beacon_get_current_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_get_current_directory, this is the rule to start with:
beacon_get_current_directory is read-only, so it stays allowed. 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_get_current_directory call is checked against it from then on.
Questions about beacon_get_current_directory
Get current working directory 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.
Register the Cobalt Strike MCP Server MCP server in PolicyLayer and add a rule for beacon_get_current_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_get_current_directory is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the beacon_get_current_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_get_current_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_get_current_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