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

spawn_net_time

Get time from target (spawn mode)

SERVERCobalt Strike MCP Server SOURCEmickeydb/cobalt-strike-mcp
High RISK CLASS
Category Execute
Parameters 00 required
Recommended Rate-limitedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/mickeydb-cobalt-strike-mcp/spawn-net-time.md

What spawn_net_time does on Cobalt Strike MCP Server

AI agents invoke spawn_net_time 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_net_time is rated High

In Cobalt Strike, 'spawn' mode means the operation forks a new process (spawns a child beacon or sacrificial process) on the compromised host to execute the command. Even though retrieving time seems benign, the act of spawning a process on a remote compromised target is an Execute-level action — it runs code on the target system.

From the tool's definition 'spawn mode' indicates spawning a new process on the target beacon to retrieve time information; part of a Cobalt Strike red team operations server with beacon control capabilities

Questions about spawn_net_time

What does the spawn_net_time tool do? +

Get time from target (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.

How do I enforce a policy on spawn_net_time? +

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

spawn_net_time is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit spawn_net_time? +

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

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

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