AI agents invoke run_all_automation_tests 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.
This tool triggers execution of automation tests within Unreal Engine, which are external operations that can perform various side effects including asset modifications, shader compilation, code generation, and system resource consumption.
From the tool's definition Tool name 'run_all_automation_tests' and description 'Run all automation tests' indicate execution of arbitrary test suites. The 'run_' prefix and verb 'Run' denote triggering external operations whose effects depend on test configuration and implementation.
Attacks that exploit this kind of access
Run all automation tests. 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.
Register the Unreal MCP server in PolicyLayer and add a rule for run_all_automation_tests: 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.
run_all_automation_tests 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 run_all_automation_tests 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 run_all_automation_tests. 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.
run_all_automation_tests is provided by the Unreal MCP server (sam-david/unreal-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →