AI agents use create_static_mesh_actor to create or update resources in Unreal — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Unreal environment.
Creating actors (3D objects) in a game engine is a reversible Write operation—new objects can be deleted or modified. It modifies the scene state but does not permanently destroy data or execute arbitrary code. Severity is medium because uncontrolled object creation could degrade performance or clutter scenes, but damage is recoverable.
From the tool's definition Tool name 'create_static_mesh_actor' indicates creation of 3D objects in Unreal Engine; sibling tools include 'delete_actor' and 'modify_actor' confirming this server manipulates scene objects. Description is empty, reducing confidence slightly.
Documented attack patterns abuse exactly the kind of access create_static_mesh_actor gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Unreal, and nothing reaches the server without passing your rules. This is the rule we recommend for create_static_mesh_actor:
{
"version": "1",
"default": "deny",
"tools": {
"create_static_mesh_actor": {
"limits": [
{
"counter": "create_static_mesh_actor_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}create_static_mesh_actor stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
create_static_mesh_actor. It is categorised as a Write tool in the Unreal MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Unreal MCP server in PolicyLayer and add a rule for create_static_mesh_actor: 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. Nothing to install.
create_static_mesh_actor is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the create_static_mesh_actor 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 create_static_mesh_actor. 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.
create_static_mesh_actor is provided by the Unreal MCP server (runeape-sats/unreal-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 21 Unreal tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
21 Unreal tools catalogued and risk-classified — across an index of 42,500+ MCP servers.