add_niagara_custom_hlsl_output

Add a typed output pin to a scratch pad module's Custom HLSL node.

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/add-niagara-custom-hlsl-output.md

What add_niagara_custom_hlsl_output does on Unreal-MCP

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

This tool modifies Unreal Engine's Niagara VFX system by adding an output pin to an existing node. It creates new editor artifacts (pins/connections) that alter the visual effects graph structure, but changes are reversible within the editor (pins can be removed, nodes re-configured).

From the tool's definition add_niagara_custom_hlsl_output: 'Add a typed output pin to a scratch pad module's Custom HLSL node' — the verb 'add' indicates creation/modification of editor state (a new output pin on a node)

Questions about add_niagara_custom_hlsl_output

What does the add_niagara_custom_hlsl_output tool do? +

Add a typed output pin to a scratch pad module's Custom HLSL node. 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 add_niagara_custom_hlsl_output? +

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

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

Can I rate-limit add_niagara_custom_hlsl_output? +

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

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

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