Get the RGBA value of a specific pixel in a texture. Args: resource_id: The texture resource ID string. x: X coordinate of the pixel. y: Y coordinate of the pixel. event_id: Optional event ID to navigate to first.
AI agents call pick_pixel to retrieve information from Renderdoc without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a straightforward query against GPU frame capture state: it fetches pixel color data from an already-loaded texture resource. This is a non-destructive, side-effect-free inspection operation typical of graphics debugging workflows. The low severity reflects that misuse cannot corrupt data, execute code, or affect systems beyond the local analysis scope.
From the tool's definition Tool retrieves RGBA pixel value from a texture—a read-only data query operation. No modification, deletion, or execution of external code occurs.
Documented attack patterns abuse exactly the kind of access pick_pixel gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Renderdoc, and nothing reaches the server without passing your rules. This is the rule we recommend for pick_pixel:
{
"version": "1",
"default": "deny",
"tools": {
"pick_pixel": {}
}
}pick_pixel is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get the RGBA value of a specific pixel in a texture. Args: resource_id: The texture resource ID string. x: X coordinate of the pixel. y: Y coordinate of the pixel. event_id: Optional event ID to navigate to first. It is categorised as a Read tool in the Renderdoc MCP Server, which means it retrieves data without modifying state.
Register the Renderdoc MCP server in PolicyLayer and add a rule for pick_pixel: 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 Renderdoc. Nothing to install.
pick_pixel 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 pick_pixel 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 pick_pixel. 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.
pick_pixel is provided by the Renderdoc MCP server (linkingooo/renderdoc-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Renderdoc, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
42 Renderdoc tools catalogued and risk-classified — across an index of 43,000+ MCP servers.