run_automation_test · Unreal MCP: Risk & Policy

WHAT IT DOES

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.

WHY IT NEEDS A POLICY

Why run_automation_test needs a policy

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

Recommended rule Ready

Verdict

run_automation_test Rate-limited

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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "run_automation_test": {
      "limits": [
        {
          "counter": "run_automation_test_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Unreal, so you can run agents against it safely.

FAQ

Questions about run_automation_test

What does the run_automation_test tool do? +

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.

How do I enforce a policy on run_automation_test? +

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.

What risk level is run_automation_test? +

run_automation_test is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit run_automation_test? +

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.

How do I block run_automation_test completely? +

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.

What MCP server provides run_automation_test? +

run_automation_test 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.