rename_blueprint_function
Rename a function in a Blueprint.
This record as markdown: /tools/aadeshrao123-unreal-mcp/rename-blueprint-function.md
What rename_blueprint_function does on Unreal-MCP
AI agents use rename_blueprint_function to create or update resources in Unreal-MCP, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Unreal-MCP environment.
Why rename_blueprint_function is rated Medium
Renaming a Blueprint function is a write operation—it creates a modified state in the project by changing metadata. It is reversible (can be undone or renamed again), so it does not qualify as Destructive. The impact is scoped to a single function's identifier within the Blueprint system, affecting only that asset's structure.
From the tool's definition Tool directly modifies a Blueprint function's name via 'rename_blueprint_function'. The description explicitly states it performs a rename operation, which is a reversible structural change to project assets.
Attacks that exploit this kind of access
The rule that runs rename_blueprint_function 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 rename_blueprint_function, this is the rule to start with:
rename_blueprint_function stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. 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 rename_blueprint_function call is checked against it from then on.
Questions about rename_blueprint_function
Rename a function in a Blueprint. It is categorised as a Write tool in the Unreal-MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Unreal MCP server in PolicyLayer and add a rule for rename_blueprint_function: 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.
rename_blueprint_function is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the rename_blueprint_function 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 rename_blueprint_function. 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.
rename_blueprint_function 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