list_device_aliases

List all device names the system knows about (dynamic catalog + static fallbacks).

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/list-device-aliases.md

WHAT IT DOES

What list_device_aliases does on Uefn

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

This is a read-only operation that queries and returns a catalog of device names. There is no data mutation, code execution, deletion, or financial impact. The blast radius of misuse is minimal — an agent can only learn what devices exist, not control them or cause harm. Low severity appropriate for passive information retrieval.

From the tool's definition Tool name is 'list_device_aliases' and description states it 'List[s] all device names' — a retrieval operation with no modification or side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

list_device_aliases Allowed

list_device_aliases 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": {
    "list_device_aliases": {}
  }
}

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 list_device_aliases call is checked against it from then on.

FAQ

Questions about list_device_aliases

What does the list_device_aliases tool do? +

List all device names the system knows about (dynamic catalog + static fallbacks). 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 list_device_aliases? +

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

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

Can I rate-limit list_device_aliases? +

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

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

list_device_aliases 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

aiva_list_affiliates on AIVA MCP Server →list_circuits on 0gzk →list_agents on 0rca Dojo MCP Server → The MCP Attack Database →

Guides

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