run_stat_command
Execute a stat console command (e.g., stat fps, stat unit, stat memory).
This record as markdown: /tools/jjpxdev-unreal-mcp/run-stat-command.md
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.
| Parameter | Type | Required | Description |
|---|---|---|---|
stat | string | Yes | Stat command (e.g., 'fps', 'unit', 'memory', 'scenerendering', 'game', 'slow') |
Parameters from the server's own tool schema.
Why run_stat_command is rated High
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
The rule that runs run_stat_command 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_stat_command, this is the rule to start with:
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.
The button opens the PolicyLayer dashboard: create your workspace, connect Unreal, apply this rule, and every run_stat_command call is checked against it from then on.
Questions about run_stat_command
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.
run_stat_command accepts 1 parameter: stat. Required: stat. 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_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.
run_stat_command 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_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.
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.
run_stat_command 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