Low Risk

editor_validate_assets

Validate assets in the project to check for errors\n\nExample output: {

How to control editor_validate_assets ↓

AI agents call editor_validate_assets to retrieve information from Unreal without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

Asset validation is a read-only diagnostic operation that queries and reports the state of assets without creating, modifying, deleting, or executing external operations. It has no side effects and presents minimal security risk if misused by an AI agent.

From the tool's definition Tool name 'editor_validate_assets' and description 'Validate assets in the project to check for errors' indicate a checking/inspection operation with no modification or deletion of assets.

Documented attack patterns abuse exactly the kind of access editor_validate_assets 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 editor_validate_assets:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "editor_validate_assets": {}
  }
}

editor_validate_assets is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Unreal — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Go deeper

What does the editor_validate_assets tool do? +

Validate assets in the project to check for errors\n\nExample output: {. It is categorised as a Read tool in the Unreal MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on editor_validate_assets? +

Register the Unreal MCP server in PolicyLayer and add a rule for editor_validate_assets: 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.

What risk level is editor_validate_assets? +

editor_validate_assets is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit editor_validate_assets? +

Yes. Add a rate_limit block to the editor_validate_assets 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.

How do I block editor_validate_assets completely? +

Set action: deny in the PolicyLayer policy for editor_validate_assets. 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.

What MCP server provides editor_validate_assets? +

editor_validate_assets is provided by the Unreal MCP server (runreal/unreal-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Unreal tool call.

Deterministic rules across all 20 Unreal tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

20 Unreal tools catalogued and risk-classified — across an index of 42,500+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.