run_map_check

Run Map Check validation on the current level.

SERVERUnreal SOURCE@jjpxdev/unreal-mcp

High RISK CLASS

Category Execute

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/jjpxdev-unreal-mcp/run-map-check.md

WHAT IT DOES

What run_map_check does on Unreal

AI agents invoke run_map_check 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.

RISK

Why run_map_check is rated High

This tool executes a validation routine (Map Check) that performs analysis and reporting on the current level state. While Map Check itself is non-destructive and intended for diagnostics, it qualifies as Execute because it triggers an external operation whose behavior and side effects depend on the current level state.

From the tool's definition The tool is named 'run_map_check' and described as 'Run Map Check validation on the current level.' The verb 'run' indicates execution of a built-in validation process within Unreal Engine that analyzes the current level for errors and inconsistencies.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs run_map_check 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_map_check, this is the rule to start with:

run_map_check Rate-limited

run_map_check 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_map_check": {
      "limits": [
        {
          "counter": "run_map_check_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Unreal, apply this rule, and every run_map_check call is checked against it from then on.

FAQ

Questions about run_map_check

What does the run_map_check tool do? +

Run Map Check validation on the current level. 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_map_check? +

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

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

Can I rate-limit run_map_check? +

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

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

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

KEEP EXPLORING

More on Unreal, and thousands of servers like it.

This server

All 127 Unreal tools → High-risk tools on this server →

Across the catalogue

editor_run_template on 010 Editor →run on 0sec →shortcuts_run on Apple Apps MCP →run_emba_scan on EMBA-MCP → All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →