get_niagara_user_parameters

A read tool on the Unreal- MCP server.

SERVERUnreal-MCP SOURCEaadeshrao123/unreal-mcp
Low RISK CLASS
Category Read
Parameters 00 required
Recommended Allowedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/aadeshrao123-unreal-mcp/get-niagara-user-parameters.md

What get_niagara_user_parameters does on Unreal-MCP

AI agents call get_niagara_user_parameters to retrieve information from Unreal-MCP without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Why get_niagara_user_parameters is rated Low

The 'get_' prefix strongly suggests data retrieval. Although the description is empty, the tool name and context (Niagara VFX system parameters) indicate this fetches existing configuration data without modifying, deleting, or executing operations. The blast radius of misuse is minimal—an agent could only read parameter values, not change engine state.

From the tool's definition The tool name 'get_niagara_user_parameters' clearly indicates a retrieval operation ('get'). Niagara is UE5's VFX system, and retrieving user parameters is a read-only query with no side effects.

Questions about get_niagara_user_parameters

What does the get_niagara_user_parameters tool do? +

get_niagara_user_parameters is a read tool on the Unreal MCP server. It is categorised as a Read tool in the Unreal-MCP MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_niagara_user_parameters? +

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

get_niagara_user_parameters is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_niagara_user_parameters? +

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

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

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

More on Unreal, and thousands of servers like it.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Unreal's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.