This record as markdown: /tools/jjpxdev-unreal-mcp/run-automation-test.md
What run_automation_test does on Unreal
AI agents invoke run_automation_test 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 |
|---|---|---|---|
test_name | string | Yes | Test name or pattern to run |
Parameters from the server's own tool schema.
Why run_automation_test is rated High
This tool triggers execution of automation tests within Unreal Engine. While testing is typically a development activity, running arbitrary automation tests can have significant side effects depending on test implementation—tests may modify project state, create/delete temporary assets, alter settings, or trigger external operations.
From the tool's definition The tool 'run_automation_test' executes a specific automation test by name. The verb 'run' combined with 'automation test' indicates active execution of arbitrary testing code whose effects depend on which test is specified as an argument.
Attacks that exploit this kind of access
The rule that runs run_automation_test 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 run_automation_test, this is the rule to start with:
run_automation_test 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 run_automation_test call is checked against it from then on.
Questions about run_automation_test
Run a specific automation test by name. 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.
run_automation_test accepts 1 parameter: test_name. Required: test_name. 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 run_automation_test: 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_automation_test 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_automation_test 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_automation_test. 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_automation_test 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