read_blueprint_content
Read complete Blueprint content: event graph, functions, variables, components.
This record as markdown: /tools/aadeshrao123-unreal-mcp/read-blueprint-content.md
What read_blueprint_content does on Unreal-MCP
AI agents call read_blueprint_content 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 read_blueprint_content is rated Low
This tool retrieves and queries Blueprint data structures without side effects. The explicit 'read' verb and list of read-only data elements (event graph, functions, variables, components) clearly indicate information retrieval only. No creation, modification, deletion, or execution of game logic occurs. This is a straightforward Read category tool with minimal risk if an AI agent misuses it.
From the tool's definition Tool name explicitly includes 'read_' prefix and description states 'Read complete Blueprint content' with operations limited to retrieval: 'event graph, functions, variables, components' — all passive data inspection with no modification, deletion, or…
Attacks that exploit this kind of access
The rule that runs read_blueprint_content 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 read_blueprint_content, this is the rule to start with:
read_blueprint_content 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 read_blueprint_content call is checked against it from then on.
Questions about read_blueprint_content
Read complete Blueprint content: event graph, functions, variables, components. 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 read_blueprint_content: 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.
read_blueprint_content 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 read_blueprint_content 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 read_blueprint_content. 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.
read_blueprint_content 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