Get parsed build errors from the latest build.
AI agents call get_build_errors to retrieve information from Unreal Editor without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and parses existing build error information from the editor's logs/diagnostics. It does not modify, execute, delete, or trigger any operations—it only queries and returns error data. The minimal blast radius of misuse would be information disclosure (log contents), not operational damage.
From the tool's definition Tool name 'get_build_errors' and description 'Get parsed build errors from the latest build' indicates retrieval of diagnostic data with no side effects. The verb 'Get' and context of 'parsed errors' (retrospective analysis) confirms read-only query semantics.
Attacks that exploit this kind of access
Get parsed build errors from the latest build. It is categorised as a Read tool in the Unreal Editor MCP Server, which means it retrieves data without modifying state.
Register the Unreal Editor MCP server in PolicyLayer and add a rule for get_build_errors: 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 Editor. Nothing to install.
get_build_errors 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 get_build_errors 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 get_build_errors. 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.
get_build_errors is provided by the Unreal Editor MCP server (tumourlove/deprecated-unreal-editor-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →