run_stat_command · Unreal MCP: Risk & Policy

WHAT IT DOES

What run_stat_command does on Unreal

AI agents invoke run_stat_command 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_stat_command needs a policy

This tool runs console commands in Unreal Engine, which is a form of code/command execution. While stat commands themselves are typically read-only diagnostics and pose lower immediate risk than destructive or financial operations, the execution capability coupled with the 'console command' abstraction creates potential for an AI agent to invoke unintended or dangerous commands if the argument parsing is exploited…

From the tool's definition Execute a stat console command — the tool explicitly enables execution of console commands within Unreal Engine's runtime environment, which are arbitrary external operations whose effects depend on arguments (e.g., stat fps, stat unit, stat memory).

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

run_stat_command Rate-limited

run_stat_command 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_stat_command": {
      "limits": [
        {
          "counter": "run_stat_command_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_stat_command

What does the run_stat_command tool do? +

Execute a stat console command (e.g., stat fps, stat unit, stat memory). 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_stat_command? +

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

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

Can I rate-limit run_stat_command? +

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

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

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