New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

device_list

List all Verse/Creative device actors in the current level with their types and locations.

SERVERUefn SOURCEquangdang46/uefn-verse-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/quangdang46-uefn-verse-mcp/device-list.md

What device_list does on Uefn

AI agents call device_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 device_list is rated Low

This tool only queries and retrieves metadata about device actors in the level—their types and locations. It performs no side effects, does not create, modify, or delete data, and does not execute operations. This is a straightforward read operation with minimal risk even if misused by an agent, as it merely exposes information already visible in the editor.

From the tool's definition Tool name and description: 'List all Verse/Creative device actors in the current level with their types and locations.' The verb 'list' and the action of retrieving information about existing actors with no modification, deletion, or execution capability.

Questions about device_list

What does the device_list tool do? +

List all Verse/Creative device actors in the current level with their types and locations. 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 device_list? +

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

What risk level is device_list? +

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

Can I rate-limit device_list? +

Yes. Add a rate_limit block to the device_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.

How do I block device_list completely? +

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

What MCP server provides device_list? +

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

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Uefn's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.