list_device_aliases

THE RISK

Low Risk

Why list_device_aliases needs a policy

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.

Documented attack patterns abuse exactly the kind of access list_device_aliases gives an agent:

POLICY

How to control list_device_aliases

PolicyLayer is an MCP gateway — it sits between your AI agents and Uefn, and nothing reaches the server without passing your rules. This is the rule we recommend for list_device_aliases:

policy.json

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

list_device_aliases is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

Create a free account and register Uefn — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

CAP THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Uefn tools

Destructive delete_actors Delete actors by their labels. Destructive delete_asset Delete an asset. Destructive tag_remove tag_remove Destructive shutdown Stop the MCP listener. Destructive snapshot_restore Restore the level to a previously saved snapshot state. Destructive undo Undo the last editor action via the transaction system. Execute batch_exec Execute multiple bridge commands in a single editor tick — faster than sending one-by-one. Execute blueprint_compile Compile a Blueprint asset and return compilation status.

All 143 Uefn tools →

Read tools on other servers

M-Team MCP Server get_torrent_detail YouTube MCP Server search_channel Android Forensics ADB MCP Server parse_browser_history 0xarchive web3_challenge

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Data exfiltration → How read access becomes an exfiltration channel when chained with untrusted content.
MCP token cost → What connecting this server costs in context-window tokens on every request.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

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.

Enforce policy on every Uefn tool call.

Start from Uefn, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →