list_displays
Lists connected displays with bounds (global space, top-left origin, points), backing scale_factor, and which is main. display_id is stable for the session so a scripted run can target the same display across steps. No permission required.
This record as markdown: /tools/com-local-mcp-local-mcp/list-displays.md
What list_displays does on Local
AI agents call list_displays to retrieve information from Local without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why list_displays is rated Low
This tool only retrieves system display information and produces no modifications, deletions, or external effects. It falls squarely into the Read category as a data retrieval operation. The low severity reflects minimal risk even if an AI agent misuses it—the worst outcome is learning about connected displays, which is generally non-sensitive system configuration data.
From the tool's definition Tool name 'list_displays' and description states it 'Lists connected displays' — a pure query operation that retrieves display metadata (bounds, scale_factor, main status) with no side effects.
Attacks that exploit this kind of access
The rule that runs list_displays safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Local, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For list_displays, this is the rule to start with:
list_displays 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 Local, apply this rule, and every list_displays call is checked against it from then on.
Questions about list_displays
Lists connected displays with bounds (global space, top-left origin, points), backing scale_factor, and which is main. display_id is stable for the session so a scripted run can target the same display across steps. No permission required. It is categorised as a Read tool in the Local MCP Server, which means it retrieves data without modifying state.
Register the Local MCP server in PolicyLayer and add a rule for list_displays: 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 Local. Nothing to install.
list_displays 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 list_displays 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 list_displays. 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.
list_displays is provided by the Local MCP server (local-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Local, and thousands of servers like it.
This server
Across the catalogue