remove_niagara_custom_hlsl_pin

Remove a pin from a Custom HLSL node and rebuild its signature.

SERVERUnreal-MCP SOURCEaadeshrao123/unreal-mcp
Critical RISK CLASS
Category Destructive
Parameters 00 required
Recommended Hiddensee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/aadeshrao123-unreal-mcp/remove-niagara-custom-hlsl-pin.md

What remove_niagara_custom_hlsl_pin does on Unreal-MCP

AI agents call remove_niagara_custom_hlsl_pin to permanently remove resources in Unreal-MCP, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Why remove_niagara_custom_hlsl_pin is rated Critical

Removing a pin from a Custom HLSL node destroys that pin's connections and configuration. This action cannot be trivially undone (unless the editor has undo history), and rebuilding the signature alters the node permanently. This fits Destructive as the most applicable category, with medium severity since it affects a single node in an Unreal Engine project rather than broader data loss.

From the tool's definition 'Remove a pin from a Custom HLSL node and rebuild its signature' — removing a pin is an irreversible structural modification that deletes part of the node's configuration

Questions about remove_niagara_custom_hlsl_pin

What does the remove_niagara_custom_hlsl_pin tool do? +

Remove a pin from a Custom HLSL node and rebuild its signature. It is categorised as a Destructive tool in the Unreal-MCP MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on remove_niagara_custom_hlsl_pin? +

Register the Unreal MCP server in PolicyLayer and add a rule for remove_niagara_custom_hlsl_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 remove_niagara_custom_hlsl_pin? +

remove_niagara_custom_hlsl_pin is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit remove_niagara_custom_hlsl_pin? +

Yes. Add a rate_limit block to the remove_niagara_custom_hlsl_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 remove_niagara_custom_hlsl_pin completely? +

Set action: deny in the PolicyLayer policy for remove_niagara_custom_hlsl_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 remove_niagara_custom_hlsl_pin? +

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

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