High Risk →

landscape

Landscape terrain: info, layers, sculpting, painting, materials, heightmap import. Actions: - get_info: Get landscape setup - list_layers: List paint layers - sample: Sample height/layers. Params: x, y - list_splines: Read landscape splines - get_component: Inspect component. Params: componentInd...

Risk signalsAccepts file system path (filePath) · High parameter count (26 properties)

Part of the Ue server.

landscape can trigger actions in Ue, with no limits today. PolicyLayer puts allow, deny, and rate-limit rules on every call. Live in minutes.

SECURE UE →

Free to start. No card required.

AI agents invoke landscape to trigger processes or run actions in Ue. Execute operations can have side effects beyond the immediate call -- triggering builds, sending notifications, or starting workflows. Rate limits and argument validation are essential to prevent runaway execution.

landscape can trigger processes with real-world consequences. An uncontrolled agent might start dozens of builds, send mass notifications, or kick off expensive compute jobs. PolicyLayer enforces rate limits and validates arguments to keep execution within safe bounds.

Execute tools trigger processes. Rate-limit and validate arguments to prevent unintended side effects.

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "landscape": {
      "limits": [
        {
          "counter": "landscape_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

See the full Ue policy for all 22 tools.

Get this rule live on your own Ue server in minutes. PolicyLayer enforces it on every call, before it runs.

ENFORCE ON MY UE →

View all 22 tools →

These attack patterns abuse exactly the kind of access landscape gives an agent. Each links to the full case and the policy that stops it:

Browse the full MCP Attack Database →

Every attack above starts with a tool call. PolicyLayer checks each one against your policy first, so landscape only ever does what you allow.

SECURE UE →

Other execute tools across the catalogue. The same approach applies to each: rate-limit and validate the arguments.

What does the landscape tool do? +

Landscape terrain: info, layers, sculpting, painting, materials, heightmap import. Actions: - get_info: Get landscape setup - list_layers: List paint layers - sample: Sample height/layers. Params: x, y - list_splines: Read landscape splines - get_component: Inspect component. Params: componentIndex - set_material: Set landscape material. Params: materialPath - add_layer_info: Register paint layer (creates LayerInfo asset + binds to active landscape). Params: layerName, packagePath?, weightBlended? - create_layer_info: Standalone LayerInfo asset creation - no landscape required. Params: layerName, name? (default LI_<layerName>), packagePath? (default /Game/Landscape/LayerInfos), physMaterial? (asset path), hardness? (#251) - create: Spawn a new ALandscape with a flat heightmap. Defaults match the Editor's Landscape Mode 'create new' (8x8 components, 63 quads/subsection, 2 subsections/component = 1016x1016 quads). Params: location? (Vec3), scale? (Vec3, default 100,100,100), componentCountX? (default 8), componentCountY? (default 8), subsectionSizeQuads? (one of 7|15|31|63|127|255, default 63), numSubsections? (1|2, default 2), heightOffset? (uint16, default 32768 = mid-elevation), label? (#303) - get_material_usage_summary: Per-proxy summary: landscape/hole material paths + component/grass/nanite counts (#150). It is categorised as a Execute tool in the Ue MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on landscape? +

Register the Ue MCP server in PolicyLayer and add a rule for landscape: 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 Ue. Nothing to install.

What risk level is landscape? +

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

Can I rate-limit landscape? +

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

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

landscape is provided by the Ue MCP server (ue-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Ue tool call.

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

Free to start. No card required.

4,600+ MCP servers and 31,000+ tools scanned and risk-classified.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.