Critical Risk →

reset_spatial_context

Reset the spatial context, clearing all tracked actors.

How to control reset_spatial_context ↓

AI agents call reset_spatial_context to permanently remove resources in Unreal — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Critical Risk

The tool clears/resets all tracked actors in the spatial context. 'Clearing' tracked state is an irreversible operation that removes the tracking information for all actors. While it may not delete the actual 3D objects themselves, it irreversibly wipes the spatial context state. The blast radius is medium since it affects the entire tracked scene context but doesn't destroy the underlying assets.

From the tool's definition Reset the spatial context, clearing all tracked actors.

Documented attack patterns abuse exactly the kind of access reset_spatial_context 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 reset_spatial_context:

policy.json
{
  "version": "1",
  "default": "deny",
  "hide": [
    "reset_spatial_context"
  ]
}

reset_spatial_context disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.

  1. Create a free account and register Unreal — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
RESTRICT THIS TOOL →

Free to start. No card required.

Go deeper

What does the reset_spatial_context tool do? +

Reset the spatial context, clearing all tracked actors. It is categorised as a Destructive tool in the Unreal MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on reset_spatial_context? +

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

reset_spatial_context is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit reset_spatial_context? +

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

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

reset_spatial_context is provided by the Unreal MCP server (runeape-sats/unreal-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Unreal tool call.

Deterministic rules across all 21 Unreal tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

21 Unreal tools catalogued and risk-classified — across an index of 42,500+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.