Get complete draw call state in a single call. Returns action info, blend, depth, stencil, rasterizer, bound textures, render targets, and shader summaries — everything needed to understand a draw call. Args: event_id: The event ID of the draw call to inspect.
AI agents call get_draw_call_state 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 is a straightforward data retrieval operation for GPU frame capture analysis. It queries existing state information from a RenderDoc capture and returns structured data for inspection purposes. No code execution, data modification, deletion, or financial operations are involved. The tool is purely informational and read-only in nature.
From the tool's definition Tool retrieves and returns draw call state information (action info, blend, depth, stencil, rasterizer, bound textures, render targets, shader summaries) without modifying, executing, or deleting any data.
Documented attack patterns abuse exactly the kind of access get_draw_call_state 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 get_draw_call_state:
{
"version": "1",
"default": "deny",
"tools": {
"get_draw_call_state": {}
}
}get_draw_call_state 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 complete draw call state in a single call. Returns action info, blend, depth, stencil, rasterizer, bound textures, render targets, and shader summaries — everything needed to understand a draw call. Args: event_id: The event ID of the draw call to inspect. 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 get_draw_call_state: 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.
get_draw_call_state 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_draw_call_state 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_draw_call_state. 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_draw_call_state 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.