device_select_by_class
Select all Verse device actors of a given class name substring.
This record as markdown: /tools/quangdang46-uefn-verse-mcp/device-select-by-class.md
What device_select_by_class does on Uefn
AI agents call device_select_by_class 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_select_by_class is rated Low
Selecting actors in the editor is a read/query operation with no persistent side effects. It changes the editor selection state temporarily but does not modify, create, or delete any data. Misuse has minimal blast radius.
From the tool's definition "Select all Verse device actors of a given class name substring" — this is a selection/query operation that identifies actors matching a class name
Attacks that exploit this kind of access
The rule that runs device_select_by_class 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 device_select_by_class, this is the rule to start with:
device_select_by_class 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 device_select_by_class call is checked against it from then on.
Questions about device_select_by_class
Select all Verse device actors of a given class name substring. 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 device_select_by_class: 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.
device_select_by_class 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 device_select_by_class 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 device_select_by_class. 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.
device_select_by_class 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