validate_assets
Run data validation on assets in a directory.
This record as markdown: /tools/jjpxdev-unreal-mcp/validate-assets.md
What validate_assets does on Unreal
AI agents invoke validate_assets to trigger actions in Unreal. 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.
| Parameter | Type | Required | Description |
|---|---|---|---|
directory | string | — | Content directory to validate |
Parameters from the server's own tool schema.
Why validate_assets is rated High
The tool actively runs/executes a validation process against assets in a directory. While validation is typically read-like in intent, 'running' a validation process in Unreal Engine may trigger plugin logic, modify asset metadata, or produce side effects depending on implementation. It is more than a simple read/query operation, placing it in Execute.
From the tool's definition 'Run data validation on assets in a directory' — 'Run' indicates active execution of a validation process
Risk signalsAccepts file system path (directory)
Attacks that exploit this kind of access
The rule that runs validate_assets 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 validate_assets, this is the rule to start with:
validate_assets 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, apply this rule, and every validate_assets call is checked against it from then on.
Questions about validate_assets
Run data validation on assets in a directory. It is categorised as a Execute tool in the Unreal MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
validate_assets accepts 1 parameter: directory. 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 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.
validate_assets 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 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.
Set action: deny in the PolicyLayer policy for 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.
validate_assets 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.
Across the catalogue