Run a console command in Unreal\n\nExample output: (No output for most commands, executed silently)\n\nExecutes the console command without returning output.
AI agents invoke editor_console_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.
This tool executes commands in the Unreal Engine console environment. While the description notes it executes 'silently' without returning output, console commands in game engines are inherently Execute-class operations because they can trigger complex side effects (asset modifications, scene changes, project settings alterations, plugin loading, etc.) whose consequences depend entirely on the command argument…
From the tool's definition Tool description states 'Run a console command in Unreal' and 'Executes the console command'. Console commands can trigger arbitrary operations in the Unreal Engine editor.
Documented attack patterns abuse exactly the kind of access editor_console_command gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Unreal, and nothing reaches the server without passing your rules. This is the rule we recommend for editor_console_command:
{
"version": "1",
"default": "deny",
"tools": {
"editor_console_command": {
"limits": [
{
"counter": "editor_console_command_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}editor_console_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.
Free to start. No card required.
Run a console command in Unreal\n\nExample output: (No output for most commands, executed silently)\n\nExecutes the console command without returning output. 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 editor_console_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.
editor_console_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 editor_console_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 editor_console_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.
editor_console_command is provided by the Unreal MCP server (runreal/unreal-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 20 Unreal tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
20 Unreal tools catalogued and risk-classified — across an index of 42,500+ MCP servers.