niagara_set_parameter
AI agents use niagara_set_parameter to create or update resources in Uefn — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Uefn environment.
The tool modifies parameter state in a Niagara system (particle effects), which is reversible and non-destructive. This aligns with Write category (creates/modifies data reversibly). Confidence is reduced due to empty description, but the name structure strongly suggests parameter modification within the UEFN editor environment, which typically supports undo/redo.
From the tool's definition Tool name 'niagara_set_parameter' indicates it sets/modifies a parameter in Niagara (Unreal's particle/visual effects system). The 'set' verb and the context of an editor tool suggest data modification. Description is empty, limiting certainty.
Documented attack patterns abuse exactly the kind of access niagara_set_parameter gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Uefn, and nothing reaches the server without passing your rules. This is the rule we recommend for niagara_set_parameter:
{
"version": "1",
"default": "deny",
"tools": {
"niagara_set_parameter": {
"limits": [
{
"counter": "niagara_set_parameter_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
} niagara_set_parameter 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.
Free to start. No card required.
niagara_set_parameter. It is categorised as a Write tool in the Uefn MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Uefn MCP server in PolicyLayer and add a rule for niagara_set_parameter: 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 Uefn. Nothing to install.
niagara_set_parameter 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 niagara_set_parameter 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 niagara_set_parameter. 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.
niagara_set_parameter is provided by the Uefn MCP server (quangdang46/uefn-verse-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Uefn, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
143 Uefn tools catalogued and risk-classified — across an index of 43,000+ MCP servers.