niagara_list_systems

THE RISK

Low Risk

Why niagara_list_systems needs a policy

This tool retrieves and displays information about existing Niagara particle system assets without modifying, executing, or deleting anything. It is a straightforward read operation with minimal risk if invoked by an AI agent.

From the tool's definition Tool name contains 'list' and description states 'List all Niagara system assets in the project' — a pure enumeration/query operation with no side effects.

Documented attack patterns abuse exactly the kind of access niagara_list_systems gives an agent:

POLICY

How to control niagara_list_systems

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_list_systems:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "niagara_list_systems": {}
  }
}

niagara_list_systems is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

Create a free account and register Uefn — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

CAP THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Uefn tools

Destructive delete_actors Delete actors by their labels. Destructive delete_asset Delete an asset. Destructive tag_remove tag_remove Destructive shutdown Stop the MCP listener. Destructive snapshot_restore Restore the level to a previously saved snapshot state. Destructive undo Undo the last editor action via the transaction system. Execute batch_exec Execute multiple bridge commands in a single editor tick — faster than sending one-by-one. Execute blueprint_compile Compile a Blueprint asset and return compilation status.

All 143 Uefn tools →

Read tools on other servers

M-Team MCP Server get_torrent_detail YouTube MCP Server search_channel Android Forensics ADB MCP Server parse_browser_history 0xarchive web3_challenge

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Data exfiltration → How read access becomes an exfiltration channel when chained with untrusted content.
MCP token cost → What connecting this server costs in context-window tokens on every request.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about niagara_list_systems

What does the niagara_list_systems tool do? +

List all Niagara system assets in the project. It is categorised as a Read tool in the Uefn MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on niagara_list_systems? +

Register the Uefn MCP server in PolicyLayer and add a rule for niagara_list_systems: 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.

What risk level is niagara_list_systems? +

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

Can I rate-limit niagara_list_systems? +

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

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

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

Enforce policy on every Uefn tool call.

Start from Uefn, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →