spawn_actor_by_class
A execute tool on the Unreal- MCP server.
This record as markdown: /tools/aadeshrao123-unreal-mcp/spawn-actor-by-class.md
What spawn_actor_by_class does on Unreal-MCP
AI agents invoke spawn_actor_by_class to trigger actions in Unreal-MCP. 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_actor_by_class is rated High
Spawning an actor in Unreal Engine by class instantiates a new object in the game world, which is an active operation with side effects in the editor/scene. This goes beyond a simple read or write — it executes engine-level functionality to create and place a live actor. Misuse could populate the scene with unintended or harmful actors. Confidence is moderate due to the empty description.
From the tool's definition Tool name 'spawn_actor_by_class' — description is empty and uninformative.
Attacks that exploit this kind of access
The rule that runs spawn_actor_by_class safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Unreal-MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For spawn_actor_by_class, this is the rule to start with:
spawn_actor_by_class 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 Unreal-MCP, apply this rule, and every spawn_actor_by_class call is checked against it from then on.
Questions about spawn_actor_by_class
spawn_actor_by_class is a execute tool on the Unreal MCP server. It is categorised as a Execute tool in the Unreal-MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Unreal MCP server in PolicyLayer and add a rule for spawn_actor_by_class: 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 Unreal-MCP. Nothing to install.
spawn_actor_by_class 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_actor_by_class 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_actor_by_class. 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_actor_by_class is provided by the Unreal MCP server (aadeshrao123/unreal-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Unreal, and thousands of servers like it.
Across the catalogue