create_npc_spawner

Generate a spawner Component that instantiates an NPC prefab over time / in escalating waves at spawn points, capped by maxAlive. RUN

SERVERSbox SOURCEsbox-mcp-server
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/sbox/create-npc-spawner.md

What create_npc_spawner does on Sbox

AI agents invoke create_npc_spawner to trigger actions in Sbox. 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 create_npc_spawner is rated High

This tool generates and runs a spawner component that continuously instantiates NPC prefabs in waves, which is an active execution/runtime operation rather than a simple write. The 'RUN' suffix confirms it executes behavior in the game engine. Misuse could flood the game scene with uncontrolled NPC spawns, but blast radius is limited to the game engine environment.

From the tool's definition 'Generate a spawner Component that instantiates an NPC prefab over time / in escalating waves' and 'RUN' — the tool triggers runtime instantiation of game objects repeatedly over time

Questions about create_npc_spawner

What does the create_npc_spawner tool do? +

Generate a spawner Component that instantiates an NPC prefab over time / in escalating waves at spawn points, capped by maxAlive. RUN. It is categorised as a Execute tool in the Sbox MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on create_npc_spawner? +

Register the Sbox MCP server in PolicyLayer and add a rule for create_npc_spawner: 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 Sbox. Nothing to install.

What risk level is create_npc_spawner? +

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

Can I rate-limit create_npc_spawner? +

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

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

create_npc_spawner is provided by the Sbox MCP server (sbox-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

More on Sbox, 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 Sbox'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.