search_niagara_functions
A read tool on the Unreal- MCP server.
This record as markdown: /tools/aadeshrao123-unreal-mcp/search-niagara-functions.md
What search_niagara_functions does on Unreal-MCP
AI agents call search_niagara_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 search_niagara_functions is rated Low
Search operations retrieve data without side effects. Even though the description is unavailable (reducing confidence slightly), the verb 'search' strongly indicates a query/lookup function that returns Niagara function information. No modification, deletion, or execution of arbitrary code is implied. Severity is low because retrieving function metadata poses minimal risk.
From the tool's definition Tool name contains 'search', which is a read-only operation. Description is empty, but the naming convention and the context of 13 tool categories in Unreal-MCP (which includes materials, blueprints, and Niagara VFX) suggest this queries or lists Niagara…
Attacks that exploit this kind of access
The rule that runs search_niagara_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 search_niagara_functions, this is the rule to start with:
search_niagara_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 search_niagara_functions call is checked against it from then on.
Questions about search_niagara_functions
search_niagara_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 search_niagara_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.
search_niagara_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 search_niagara_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 search_niagara_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.
search_niagara_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