AI agents call screen.list_displays to retrieve information from Third Eye without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries system display configuration and returns metadata (index, name, position, dimensions, primary status). It performs read-only enumeration with no capability to modify, execute, delete, or capture data. The information returned is static system metadata that does not require elevated privilege to access, making this a straightforward Read category risk with low severity.
From the tool's definition Tool name 'list_displays' and description 'List all available displays/monitors with their properties' indicates retrieval of display information without modification or side effects.
Attacks that exploit this kind of access
List all available displays/monitors with their properties (index, name, position, dimensions, primary status). It is categorised as a Read tool in the Third Eye MCP Server, which means it retrieves data without modifying state.
Register the Third Eye MCP server in PolicyLayer and add a rule for screen.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 Third Eye. Nothing to install.
screen.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 screen.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 screen.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.
screen.list_displays is provided by the Third Eye MCP server (osseni94/third-eye-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →