Low Risk

get_spatial_context

Return the current spatial context of all actors as a JSON string.

How to control get_spatial_context ↓

AI agents call get_spatial_context to retrieve information from Unreal without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

This tool queries and retrieves spatial information about actors in the Unreal Engine scene. It is purely informational with no capability to modify, delete, or execute operations. The blast radius of misuse is minimal—an AI agent could only gather scene information, not alter the scene or trigger external effects.

From the tool's definition Tool name is 'get_spatial_context' and description states 'Return the current spatial context of all actors as a JSON string.' The verb 'Return' and action 'get' indicate data retrieval with no modification or side effects.

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

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_spatial_context": {}
  }
}

get_spatial_context is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  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.
CAP THIS TOOL →

Free to start. No card required.

Go deeper

What does the get_spatial_context tool do? +

Return the current spatial context of all actors as a JSON string. It is categorised as a Read tool in the Unreal MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_spatial_context? +

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

get_spatial_context is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_spatial_context? +

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

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

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