Critical Risk →

reset_basic_castle

Delete a castle by prefix.

How to control reset_basic_castle ↓

AI agents call reset_basic_castle 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

This tool permanently removes objects from the scene without the ability to undo through the tool itself. Deletion of game objects is irreversible data destruction. While the blast radius is somewhat contained to a specific scene/project, the high confidence in destructive capability and potential for accidental mass deletion (via prefix matching) warrants 'high' severity rather than 'critical', as it does not…

From the tool's definition Tool description states 'Delete a castle by prefix', indicating irreversible deletion of 3D objects/assets in the Unreal Engine scene.

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

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

reset_basic_castle 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_basic_castle tool do? +

Delete a castle by prefix. 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_basic_castle? +

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

reset_basic_castle 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_basic_castle? +

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

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

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