reimport_skeletal_mesh
Reimport a skeletal mesh from its source file.
This record as markdown: /tools/jjpxdev-unreal-mcp/reimport-skeletal-mesh.md
What reimport_skeletal_mesh does on Unreal
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.
| Parameter | Type | Required | Description |
|---|---|---|---|
mesh_path | string | Yes | Skeletal mesh asset path |
Parameters from the server's own tool schema.
Why reimport_skeletal_mesh is rated Medium
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
The rule that runs reimport_skeletal_mesh safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Unreal, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For reimport_skeletal_mesh, this is the rule to start with:
reimport_skeletal_mesh 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Unreal, apply this rule, and every reimport_skeletal_mesh call is checked against it from then on.
Questions about reimport_skeletal_mesh
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.
reimport_skeletal_mesh accepts 1 parameter: mesh_path. Required: mesh_path. The full parameter table on this page comes from the server's own tool schema.
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 (@jjpxdev/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.
This server
Across the catalogue