Get the RGB color of a pixel at specific coordinates.
AI agents call get_pixel_color to retrieve information from macOS Control MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool only reads pixel color data from the screen without modifying state, executing code, or triggering external operations. It is informational and non-destructive, fitting the Read category. The severity is low because the blast radius of misuse is minimal—an adversary could only observe visual information about the screen state.
From the tool's definition The tool 'get_pixel_color' retrieves the RGB color value at specific screen coordinates. The description explicitly states it 'Get[s] the RGB color' with no mention of modification, deletion, or execution of actions.
Attacks that exploit this kind of access
Get the RGB color of a pixel at specific coordinates. It is categorised as a Read tool in the macOS Control MCP Server MCP Server, which means it retrieves data without modifying state.
Register the macOS Control MCP Server MCP server in PolicyLayer and add a rule for get_pixel_color: 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 macOS Control MCP Server. Nothing to install.
get_pixel_color 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 get_pixel_color 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 get_pixel_color. 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.
get_pixel_color is provided by the macOS Control MCP Server MCP server (lodimup/macos-control-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 →