spawn_portscan
Perform port scan (spawn mode)
This record as markdown: /tools/mickeydb-cobalt-strike-mcp/spawn-portscan.md
What spawn_portscan does on Cobalt Strike MCP Server
AI agents invoke spawn_portscan 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.
Why spawn_portscan is rated High
Port scanning is an active network reconnaissance operation that spawns external processes and sends network probes to discover open ports on target systems. This is an Execute-category action with high severity because it triggers external operations against potentially unauthorized targets, is a core red team/offensive security capability, and could facilitate unauthorized access or be used maliciously.
From the tool's definition 'Perform port scan (spawn mode)' - spawns a process to conduct network port scanning
Attacks that exploit this kind of access
The rule that runs spawn_portscan 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 spawn_portscan, this is the rule to start with:
spawn_portscan 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Cobalt Strike MCP Server, apply this rule, and every spawn_portscan call is checked against it from then on.
Questions about spawn_portscan
Perform port scan (spawn mode). 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.
Register the Cobalt Strike MCP Server MCP server in PolicyLayer and add a rule for spawn_portscan: 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.
spawn_portscan is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the spawn_portscan 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 spawn_portscan. 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.
spawn_portscan 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.
Across the catalogue