open_asset
Open an asset in the UE5 editor (blueprint, material, data table, widget, etc.).
This record as markdown: /tools/aadeshrao123-unreal-mcp/open-asset.md
What open_asset does on Unreal-MCP
AI agents invoke open_asset 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 open_asset is rated High
Opening an asset triggers an external operation in the Unreal Engine 5 editor, causing the editor to load and display the asset. This is not a simple read (no data is returned to the caller) nor a write (no data is modified), but rather an action that triggers an external editor operation.
From the tool's definition Open an asset in the UE5 editor (blueprint, material, data table, widget, etc.)
Attacks that exploit this kind of access
The rule that runs open_asset 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 open_asset, this is the rule to start with:
open_asset 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 open_asset call is checked against it from then on.
Questions about open_asset
Open an asset in the UE5 editor (blueprint, material, data table, widget, etc.). 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 open_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-MCP. Nothing to install.
open_asset 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 open_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 open_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.
open_asset 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