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

spawn_process_list

List processes 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/spawn-process-list.md

What spawn_process_list does on Cobalt Strike MCP Server

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

This tool retrieves process information from a compromised endpoint (beacon) without modifying or destroying anything. It is fundamentally a read operation. Severity is high because Cobalt Strike is a red team/attack framework and this tool provides reconnaissance data that could be used to identify security software, determine lateral movement targets, or find privilege escalation opportunities.

From the tool's definition Tool name and description indicate it 'List processes on a beacon' - a query/retrieval operation with no modification or deletion of data or system state.

Questions about spawn_process_list

What does the spawn_process_list tool do? +

List processes 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 spawn_process_list? +

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

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

Can I rate-limit spawn_process_list? +

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

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

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