get_material_errors
Get shader compilation errors for a material.
This record as markdown: /tools/aadeshrao123-unreal-mcp/get-material-errors.md
What get_material_errors does on Unreal-MCP
AI agents call get_material_errors to retrieve information from Unreal-MCP without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why get_material_errors is rated Low
This tool retrieves error diagnostics from the Unreal Engine editor about shader compilation. It performs no state changes, does not execute code, does not create or delete assets, and does not trigger side effects. It is purely informational—reading existing error data. This is a safe Read operation with low risk, as misuse would only surface existing error information without enabling harmful actions.
From the tool's definition Tool name 'get_material_errors' and description 'Get shader compilation errors for a material' indicate retrieval/query of diagnostic information with no modification or execution.
Attacks that exploit this kind of access
The rule that runs get_material_errors safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Unreal-MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_material_errors, this is the rule to start with:
get_material_errors is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Unreal-MCP, apply this rule, and every get_material_errors call is checked against it from then on.
Questions about get_material_errors
Get shader compilation errors for a material. It is categorised as a Read tool in the Unreal-MCP MCP Server, which means it retrieves data without modifying state.
Register the Unreal MCP server in PolicyLayer and add a rule for get_material_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-MCP. Nothing to install.
get_material_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_material_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_material_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_material_errors is provided by the Unreal MCP server (aadeshrao123/unreal-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Unreal, and thousands of servers like it.
This server
Across the catalogue