This record as markdown: /tools/jjpxdev-unreal-mcp/reset-niagara-system.md
What reset_niagara_system does on Unreal
AI agents invoke reset_niagara_system to trigger actions in Unreal. 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.
| Parameter | Type | Required | Description |
|---|---|---|---|
actor_name | string | Yes | Actor with Niagara component |
Parameters from the server's own tool schema.
Why reset_niagara_system is rated High
Resetting a Niagara particle system triggers an external operation within Unreal Engine (restarting the particle simulation on an actor). It is not a simple read, nor does it irreversibly delete data. It executes a runtime action whose effects depend on which actor/system is targeted, placing it in the Execute category.
From the tool's definition Reset a Niagara system on an actor
Attacks that exploit this kind of access
The rule that runs reset_niagara_system safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Unreal, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For reset_niagara_system, this is the rule to start with:
reset_niagara_system 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Unreal, apply this rule, and every reset_niagara_system call is checked against it from then on.
Questions about reset_niagara_system
Reset a Niagara system on an actor. It is categorised as a Execute tool in the Unreal MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
reset_niagara_system accepts 1 parameter: actor_name. Required: actor_name. The full parameter table on this page comes from the server's own tool schema.
Register the Unreal MCP server in PolicyLayer and add a rule for reset_niagara_system: 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. Nothing to install.
reset_niagara_system is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the reset_niagara_system 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 reset_niagara_system. 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.
reset_niagara_system is provided by the Unreal MCP server (@jjpxdev/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.
Across the catalogue