light_list
List all light actors in the level with their types and properties.
This record as markdown: /tools/quangdang46-uefn-verse-mcp/light-list.md
What light_list does on Uefn
AI agents call light_list to retrieve information from Uefn without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why light_list is rated Low
This tool retrieves information about existing light actors in an Unreal Editor level. It performs a read-only operation that queries and returns data without modifying, deleting, or executing any changes to the level state. The verb 'list' is characteristic of Read category tools. No irreversible actions, code execution, or data modification occurs.
From the tool's definition Tool name 'light_list' and description 'List all light actors in the level with their types and properties' indicate a query/retrieval operation with no side effects.
Attacks that exploit this kind of access
The rule that runs light_list safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Uefn, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For light_list, this is the rule to start with:
light_list 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 Uefn, apply this rule, and every light_list call is checked against it from then on.
Questions about light_list
List all light actors in the level with their types and properties. It is categorised as a Read tool in the Uefn MCP Server, which means it retrieves data without modifying state.
Register the Uefn MCP server in PolicyLayer and add a rule for light_list: 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.
light_list 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 light_list 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 light_list. 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.
light_list 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.
More on Uefn, and thousands of servers like it.
This server
Across the catalogue