spawn_niagara_effect

A execute tool on the Unreal- MCP server.

SERVERUnreal-MCP SOURCEaadeshrao123/unreal-mcp

High RISK CLASS

Category Execute

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/spawn-niagara-effect.md

WHAT IT DOES

What spawn_niagara_effect does on Unreal-MCP

AI agents invoke spawn_niagara_effect to trigger actions in Unreal-MCP. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.

RISK

Why spawn_niagara_effect is rated High

Based on the name, this tool likely spawns/instantiates a Niagara VFX particle effect in the Unreal Engine editor or scene. 'Spawning' an effect is an external operation that triggers something in the engine environment. With no description to confirm behavior, confidence is reduced.

From the tool's definition Tool name 'spawn_niagara_effect' — no description provided.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

spawn_niagara_effect Rate-limited

spawn_niagara_effect stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "spawn_niagara_effect": {
      "limits": [
        {
          "counter": "spawn_niagara_effect_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-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 spawn_niagara_effect call is checked against it from then on.

FAQ

Questions about spawn_niagara_effect

What does the spawn_niagara_effect tool do? +

spawn_niagara_effect is a execute tool on the Unreal MCP server. It is categorised as a Execute tool in the Unreal-MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on spawn_niagara_effect? +

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

spawn_niagara_effect is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit spawn_niagara_effect? +

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

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

spawn_niagara_effect 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 → High-risk tools on this server →

Across the catalogue

spawn on Frida Game Hacking MCP → All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →