AI agents use reimport_skeletal_mesh 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.
This tool modifies skeletal mesh assets by reimporting them, which is a reversible write operation. While it affects game assets and could impact project state if misused (e.g., importing corrupted or malicious mesh data), it does not delete data (Destructive), execute arbitrary code (Execute), cause financial transactions (Financial), or merely read data (Read).
From the tool's definition Tool name 'reimport_skeletal_mesh' and description 'Reimport a skeletal mesh from its source file' indicate modification of existing assets by reloading/updating them from source.
Attacks that exploit this kind of access
Reimport a skeletal mesh from its source file. 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 reimport_skeletal_mesh: 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.
reimport_skeletal_mesh 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 reimport_skeletal_mesh 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 reimport_skeletal_mesh. 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.
reimport_skeletal_mesh is provided by the Unreal MCP server (sam-david/unreal-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →