lvgl_list_devices

List ESPHome devices that have LVGL display support (lvgl: key present in config).

SERVERHa Nexus Agent SOURCEfistacho/ha-nexus-agent

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/fistacho-ha-nexus-agent/lvgl-list-devices.md

WHAT IT DOES

What lvgl_list_devices does on Ha Nexus Agent

AI agents call lvgl_list_devices to retrieve information from Ha Nexus Agent without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why lvgl_list_devices is rated Low

This tool retrieves and filters information about ESPHome devices based on their configuration (presence of lvgl key). It is a read-only operation that returns data without creating, modifying, deleting, or executing any changes. The blast radius of misuse is minimal—an agent could only gain visibility into which devices have LVGL support, posing no direct harm to the smart home system.

From the tool's definition Tool name 'lvgl_list_devices' and description 'List ESPHome devices that have LVGL display support' indicate a query/retrieval operation with no modification or side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs lvgl_list_devices safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Ha Nexus Agent, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For lvgl_list_devices, this is the rule to start with:

lvgl_list_devices Allowed

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

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

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

FAQ

Questions about lvgl_list_devices

What does the lvgl_list_devices tool do? +

List ESPHome devices that have LVGL display support (lvgl: key present in config). It is categorised as a Read tool in the Ha Nexus Agent MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on lvgl_list_devices? +

Register the Ha Nexus Agent MCP server in PolicyLayer and add a rule for lvgl_list_devices: 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 Ha Nexus Agent. Nothing to install.

What risk level is lvgl_list_devices? +

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

Can I rate-limit lvgl_list_devices? +

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

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

lvgl_list_devices is provided by the Ha Nexus Agent MCP server (fistacho/ha-nexus-agent). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Ha Nexus Agent, and thousands of servers like it.

This server

All 309 Ha Nexus Agent 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 →