execute_beacon_info

Get beacon information

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/execute-beacon-info.md

WHAT IT DOES

What execute_beacon_info does on Cobalt Strike MCP Server

AI agents call execute_beacon_info 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 execute_beacon_info is rated Low

The tool appears to retrieve/query beacon information (a Read operation). However, the context is a Cobalt Strike red team C2 framework, meaning even read operations expose sensitive operational security data about compromised hosts, active implants, and attacker infrastructure. The 'execute_' prefix is somewhat misleading given the description says 'Get', lowering confidence slightly.

From the tool's definition Tool name 'execute_beacon_info' and description 'Get beacon information' — retrieves data about a beacon.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

execute_beacon_info Allowed

execute_beacon_info 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": {
    "execute_beacon_info": {}
  }
}

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

FAQ

Questions about execute_beacon_info

What does the execute_beacon_info tool do? +

Get beacon information. 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 execute_beacon_info? +

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

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

Can I rate-limit execute_beacon_info? +

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

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

execute_beacon_info 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

The MCP Attack Database →

Guides

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