Get the full modification history of a pixel across all events in the frame. Shows every event that wrote to this pixel, with before/after values and pass/fail status (depth test, stencil test, etc.). Args: resource_id: The texture resource ID (must be a render target). x: X coordinate of the pix...
AI agents call pixel_history 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 retrieves and displays historical data about pixel modifications within an already-loaded RenderDoc frame capture. It is a passive inspection and analysis capability with no side effects, data modification, code execution, or destructive potential. The tool operates entirely within the context of analyzing static GPU frame capture data.
From the tool's definition Tool description states it 'Get[s] the full modification history' and 'Shows every event that wrote to this pixel' — the language is purely informational (get, show).
Risk signalsBulk/mass operation — affects multiple targets
Documented attack patterns abuse exactly the kind of access pixel_history 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 pixel_history:
{
"version": "1",
"default": "deny",
"tools": {
"pixel_history": {}
}
}pixel_history 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 full modification history of a pixel across all events in the frame. Shows every event that wrote to this pixel, with before/after values and pass/fail status (depth test, stencil test, etc.). Args: resource_id: The texture resource ID (must be a render target). 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 pixel_history: 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.
pixel_history 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 pixel_history 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 pixel_history. 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.
pixel_history 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.