AI agents invoke run_gauntlet 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.
The tool triggers execution of arbitrary test suites (Gauntlet tests) within a live Unreal Engine game instance via the Unreal Automation Tool (UAT). This is a code execution action whose effects depend entirely on what tests are specified—tests could interact with game state, modify assets, access sensitive data, or cause unpredictable side effects.
From the tool's definition Tool description explicitly states 'Launch a Gauntlet test session via UAT' and 'Runs tests in a full game instance.' These clearly indicate execution of test code within a game runtime environment.
Attacks that exploit this kind of access
Launch a Gauntlet test session via UAT. Runs tests in a full game instance. 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_gauntlet: 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_gauntlet 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_gauntlet 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_gauntlet. 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_gauntlet 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 →