add_niagara_custom_hlsl_input
Add a typed input pin to a scratch pad module's Custom HLSL node.
This record as markdown: /tools/aadeshrao123-unreal-mcp/add-niagara-custom-hlsl-input.md
What add_niagara_custom_hlsl_input does on Unreal-MCP
AI agents use add_niagara_custom_hlsl_input 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_input is rated Medium
This tool creates or modifies VFX node structure within Unreal Engine's Niagara system. The 'add' verb and the action of introducing a new input pin represent reversible modifications to editor state. While it affects VFX logic, the changes can be undone through normal editor operations (undo/deletion).
From the tool's definition Tool name 'add_niagara_custom_hlsl_input' and description 'Add a typed input pin to a scratch pad module's Custom HLSL node' indicate the tool modifies Niagara VFX system configuration by adding a new input parameter.
Attacks that exploit this kind of access
The rule that runs add_niagara_custom_hlsl_input 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 add_niagara_custom_hlsl_input, this is the rule to start with:
add_niagara_custom_hlsl_input 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 add_niagara_custom_hlsl_input call is checked against it from then on.
Questions about add_niagara_custom_hlsl_input
Add a typed input 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.
Register the Unreal MCP server in PolicyLayer and add a rule for add_niagara_custom_hlsl_input: 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.
add_niagara_custom_hlsl_input 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 add_niagara_custom_hlsl_input 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 add_niagara_custom_hlsl_input. 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.
add_niagara_custom_hlsl_input 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