list_niagara_data_interface_functions
A read tool on the Unreal- MCP server.
This record as markdown: /tools/aadeshrao123-unreal-mcp/list-niagara-data-interface-functions.md
What list_niagara_data_interface_functions does on Unreal-MCP
AI agents call list_niagara_data_interface_functions 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 list_niagara_data_interface_functions is rated Low
The tool lists (retrieves) available Niagara data interface functions—a read-only operation with no side effects. Despite the empty description reducing confidence slightly, the naming convention clearly indicates data retrieval. In the Unreal editor context, this is analogous to querying available API functions, which is a safe informational lookup.
From the tool's definition Tool name 'list_niagara_data_interface_functions' uses the verb 'list', which indicates retrieval of information without modification. The context describes a server controlling Unreal Engine 5 editor, and listing functions is a query operation.
Attacks that exploit this kind of access
The rule that runs list_niagara_data_interface_functions 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 list_niagara_data_interface_functions, this is the rule to start with:
list_niagara_data_interface_functions is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Unreal-MCP, apply this rule, and every list_niagara_data_interface_functions call is checked against it from then on.
Questions about list_niagara_data_interface_functions
list_niagara_data_interface_functions 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.
Register the Unreal MCP server in PolicyLayer and add a rule for list_niagara_data_interface_functions: 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.
list_niagara_data_interface_functions is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the list_niagara_data_interface_functions 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 list_niagara_data_interface_functions. 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.
list_niagara_data_interface_functions 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.
This server
Across the catalogue