run_automation_tests_by_category · Unreal MCP: Risk & Policy

WHAT IT DOES

What run_automation_tests_by_category does on Unreal

AI agents invoke run_automation_tests_by_category 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_tests_by_category needs a policy

This tool executes automation tests, which is an external operation whose effects depend on the category pattern argument provided. While tests are typically non-destructive by design, the tool triggers execution of arbitrary test code that could have side effects depending on test implementation (test data creation, state changes, etc.).

From the tool's definition Tool name 'run_automation_tests_by_category' combined with description 'Run automation tests matching a category pattern' indicates execution of test suites. The verb 'Run' and the fact it triggers automation tests demonstrate code execution capability.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

run_automation_tests_by_category Rate-limited

run_automation_tests_by_category 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_tests_by_category": {
      "limits": [
        {
          "counter": "run_automation_tests_by_category_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_tests_by_category

What does the run_automation_tests_by_category tool do? +

Run automation tests matching a category pattern. 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_tests_by_category? +

Register the Unreal MCP server in PolicyLayer and add a rule for run_automation_tests_by_category: 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_tests_by_category? +

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

Can I rate-limit run_automation_tests_by_category? +

Yes. Add a rate_limit block to the run_automation_tests_by_category 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_tests_by_category completely? +

Set action: deny in the PolicyLayer policy for run_automation_tests_by_category. 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_tests_by_category? +

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