get_niagara_graph_nodes

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-graph-nodes.md

WHAT IT DOES

What get_niagara_graph_nodes does on Unreal-MCP

AI agents call get_niagara_graph_nodes 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.

RISK

Why get_niagara_graph_nodes is rated Low

The tool appears to query or list nodes within a Niagara graph, consistent with Read category behavior (retrieves data without side effects). The empty description reduces confidence slightly, but the naming pattern and context within a VFX editor (alongside other node-manipulation tools) strongly suggests this is a query operation.

From the tool's definition Tool name 'get_niagara_graph_nodes' indicates retrieval of graph node data from Niagara VFX system. The 'get_' prefix is conventionally associated with read-only queries. No description provided.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs get_niagara_graph_nodes safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Unreal-MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_niagara_graph_nodes, this is the rule to start with:

get_niagara_graph_nodes Allowed

get_niagara_graph_nodes is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

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

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Unreal-MCP, apply this rule, and every get_niagara_graph_nodes call is checked against it from then on.

FAQ

Questions about get_niagara_graph_nodes

What does the get_niagara_graph_nodes tool do? +

get_niagara_graph_nodes 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_graph_nodes? +

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

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

Can I rate-limit get_niagara_graph_nodes? +

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

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

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

KEEP EXPLORING

More on Unreal, and thousands of servers like it.

This server

All 286 Unreal tools →

Across the catalogue

get_cocktail_by_category on Cocktails RAG MCP Server →get_torrent_detail on M-Team MCP Server →aiva_get_affiliate on AIVA MCP Server →get-chuck-categories on Jokes MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →