This record as markdown: /tools/jjpxdev-unreal-mcp/export-asset.md
What export_asset does on Unreal
AI agents use export_asset 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 |
|---|---|---|---|
asset_path | string | Yes | Asset to export |
output_path | string | Yes | Output file path on disk |
Parameters from the server's own tool schema.
Why export_asset is rated Medium
Exporting assets creates new files on disk and could potentially overwrite existing files depending on implementation. While not destructive (original asset remains intact) and not as severe as file deletion, it represents a write operation with moderate risk if misused—an AI agent could export sensitive assets, large volumes of data, or corrupt export formats.
From the tool's definition Tool name 'export_asset' and description 'Export an asset to an external file format' indicate the tool creates or writes data to external files. This is a write operation that modifies the file system by generating new files.
Attacks that exploit this kind of access
The rule that runs export_asset 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 export_asset, this is the rule to start with:
export_asset 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 export_asset call is checked against it from then on.
Questions about export_asset
Export an asset to an external file format. 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.
export_asset accepts 2 parameters: asset_path, output_path. Required: asset_path, output_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 export_asset: 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.
export_asset 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 export_asset 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 export_asset. 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.
export_asset 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