set_niagara_vector
Set a vector parameter on a Niagara component.
This record as markdown: /tools/jjpxdev-unreal-mcp/set-niagara-vector.md
What set_niagara_vector does on Unreal
AI agents use set_niagara_vector to create or update resources in Unreal, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Unreal environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
value | object | Yes | Vector value |
actor_name | string | Yes | Actor with Niagara component |
parameter_name | string | Yes | Parameter name |
Parameters from the server's own tool schema.
Why set_niagara_vector is rated Medium
This tool modifies visual/simulation parameters on a Niagara component (Unreal's particle effects system) by setting a vector parameter. This is a reversible write operation—changes can be undone by setting different values. It does not execute arbitrary code, delete data, or cause financial impact.
From the tool's definition Tool name 'set_niagara_vector' and description 'Set a vector parameter on a Niagara component' indicate modification of a parameter on an existing Niagara (particle system) component.
Attacks that exploit this kind of access
The rule that runs set_niagara_vector 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 set_niagara_vector, this is the rule to start with:
set_niagara_vector 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, apply this rule, and every set_niagara_vector call is checked against it from then on.
Questions about set_niagara_vector
Set a vector parameter on a Niagara component. It is categorised as a Write tool in the Unreal MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
set_niagara_vector accepts 3 parameters: value, actor_name, parameter_name. Required: value, actor_name, parameter_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 set_niagara_vector: 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.
set_niagara_vector 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 set_niagara_vector 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 set_niagara_vector. 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.
set_niagara_vector 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.
This server
Across the catalogue