Low Risk

get_unreal_engine_path

Get the current Unreal Engine path

How to control get_unreal_engine_path ↓

AI agents call get_unreal_engine_path 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 only retrieves and returns the path to the Unreal Engine installation—a read-only operation with no side effects, no data modification, no code execution, and no destructive impact. It is informational only.

From the tool's definition Tool name 'get_unreal_engine_path' and description 'Get the current Unreal Engine path' indicate a simple query operation that retrieves configuration/path information without modifying any state.

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

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

get_unreal_engine_path 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_unreal_engine_path tool do? +

Get the current Unreal Engine path. 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_unreal_engine_path? +

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

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

Can I rate-limit get_unreal_engine_path? +

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

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

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

Enforce policy on every Unreal tool call.

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.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.