rename_niagara_node_pin

Rename a dynamic pin on any node in a scratch pad graph.

SERVERUnreal-MCP SOURCEaadeshrao123/unreal-mcp
Medium RISK CLASS
Category Write
Parameters 00 required
Recommended Rate-limitedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/aadeshrao123-unreal-mcp/rename-niagara-node-pin.md

What rename_niagara_node_pin does on Unreal-MCP

AI agents use rename_niagara_node_pin 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_niagara_node_pin is rated Medium

Renaming a node pin is a reversible modification of asset metadata (the pin's name/label) within the Unreal Engine editor. This is a Write operation because it creates or modifies data reversibly. The severity is medium because incorrect renames could break node connections or create workflow confusion, but the effect is limited to a single pin and is easily undone via undo operations typical in modern editors.

From the tool's definition Tool explicitly performs 'Rename' action on a pin within a Niagara node in a scratch pad graph, which modifies metadata of an existing asset without deleting or executing arbitrary code.

Questions about rename_niagara_node_pin

What does the rename_niagara_node_pin tool do? +

Rename a dynamic pin on any node in a scratch pad graph. 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.

How do I enforce a policy on rename_niagara_node_pin? +

Register the Unreal MCP server in PolicyLayer and add a rule for rename_niagara_node_pin: 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.

What risk level is rename_niagara_node_pin? +

rename_niagara_node_pin is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit rename_niagara_node_pin? +

Yes. Add a rate_limit block to the rename_niagara_node_pin 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.

How do I block rename_niagara_node_pin completely? +

Set action: deny in the PolicyLayer policy for rename_niagara_node_pin. 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.

What MCP server provides rename_niagara_node_pin? +

rename_niagara_node_pin 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.

Across the catalogue

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Unreal's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.