resolve_niagara_built_in_dynamic_input

A write tool on the Unreal- MCP server.

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/resolve-niagara-built-in-dynamic-input.md

WHAT IT DOES

What resolve_niagara_built_in_dynamic_input does on Unreal-MCP

AI agents use resolve_niagara_built_in_dynamic_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.

RISK

Why resolve_niagara_built_in_dynamic_input is rated Medium

Based on the pattern of sibling tools and the context of Unreal Engine editor control, this tool most likely modifies Niagara VFX system configuration (Write category). The high severity reflects that misuse could corrupt VFX pipelines or editor state across dependent assets.

From the tool's definition Tool name contains 'resolve' and 'Niagara' (Unreal's VFX system). Sibling tools like 'add_blueprint_node', 'add_component_to_blueprint', 'add_data_table_row' are all Write operations that modify editor state.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

resolve_niagara_built_in_dynamic_input Rate-limited

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

View as policy code

policy.json

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

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Unreal-MCP, apply this rule, and every resolve_niagara_built_in_dynamic_input call is checked against it from then on.

FAQ

Questions about resolve_niagara_built_in_dynamic_input

What does the resolve_niagara_built_in_dynamic_input tool do? +

resolve_niagara_built_in_dynamic_input is a write tool on the Unreal MCP server. 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 resolve_niagara_built_in_dynamic_input? +

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

What risk level is resolve_niagara_built_in_dynamic_input? +

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

Can I rate-limit resolve_niagara_built_in_dynamic_input? +

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

How do I block resolve_niagara_built_in_dynamic_input completely? +

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

What MCP server provides resolve_niagara_built_in_dynamic_input? +

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

KEEP EXPLORING

More on Unreal, and thousands of servers like it.

This server

All 286 Unreal tools →

Across the catalogue

The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →