device_select_by_name

Select all Verse device actors whose label contains the filter string.

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-select-by-name.md

WHAT IT DOES

What device_select_by_name does on Uefn

AI agents call device_select_by_name 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.

RISK

Why device_select_by_name is rated Low

Selecting actors by name is a read/query operation within the editor UI. It does not modify, create, or delete any data; it simply identifies and selects matching actors in the viewport. The blast radius if misused is minimal - at worst, unwanted actors get selected in the editor.

From the tool's definition 'Select all Verse device actors whose label contains the filter string' - this is a selection/query operation that retrieves/highlights actors matching a filter

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs device_select_by_name 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_name, this is the rule to start with:

device_select_by_name Allowed

device_select_by_name is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "device_select_by_name": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Uefn, apply this rule, and every device_select_by_name call is checked against it from then on.

FAQ

Questions about device_select_by_name

What does the device_select_by_name tool do? +

Select all Verse device actors whose label contains the filter string. 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_select_by_name? +

Register the Uefn MCP server in PolicyLayer and add a rule for device_select_by_name: 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_select_by_name? +

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

Can I rate-limit device_select_by_name? +

Yes. Add a rate_limit block to the device_select_by_name 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_select_by_name completely? +

Set action: deny in the PolicyLayer policy for device_select_by_name. 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_select_by_name? +

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

KEEP EXPLORING

More on Uefn, and thousands of servers like it.

This server

All 143 Uefn tools →

Across the catalogue

get_cocktail_by_name on Cocktails RAG MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →