rename_niagara_custom_hlsl_pin

What rename_niagara_custom_hlsl_pin does on Unreal-MCP

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

This tool creates or modifies data within an Unreal Engine project (custom HLSL pins and their references). The operations are reversible—an AI agent could later rename them back or undo changes. While it affects shader code execution indirectly through pin/reference changes, the primary action is data modification (renaming and updating references), not executing arbitrary code or triggering irreversible deletion.

From the tool's definition Tool explicitly performs 'Rename' and 'update references' operations on Niagara custom HLSL pins and their source, which modifies project data (shader pin names and references) reversibly within the Unreal Engine editor.

The rule that runs rename_niagara_custom_hlsl_pin 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_niagara_custom_hlsl_pin, this is the rule to start with:

{
  "version": "1",
  "default": "deny",
  "tools": {
    "rename_niagara_custom_hlsl_pin": {
      "limits": [
        {
          "counter": "rename_niagara_custom_hlsl_pin_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

Questions about rename_niagara_custom_hlsl_pin