Verify that a castle built from the shared plan exists in the current level.
AI agents call verify_basic_castle 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.
This tool performs a verification query on the current level state to confirm the existence of a previously created castle. It retrieves or inspects data to determine if a specific object exists, with no side effects, modifications, or external operations. This is consistent with Read category operations like 'get', 'check', or 'verify'.
From the tool's definition Tool name 'verify_basic_castle' and description 'Verify that a castle built from the shared plan exists in the current level' indicate a query/check operation. The verb 'verify' is a read operation that checks state without modification.
Documented attack patterns abuse exactly the kind of access verify_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 verify_basic_castle:
{
"version": "1",
"default": "deny",
"tools": {
"verify_basic_castle": {}
}
}verify_basic_castle is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Verify that a castle built from the shared plan exists in the current level. It is categorised as a Read tool in the Unreal MCP Server, which means it retrieves data without modifying state.
Register the Unreal MCP server in PolicyLayer and add a rule for verify_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.
verify_basic_castle is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the verify_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.
Set action: deny in the PolicyLayer policy for verify_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.
verify_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.
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.