// MCP TOOL REFERENCE

RENDERDOC TOOLS

42 tools from the Renderdoc MCP Server, categorised by risk level.

// ALL 42 RENDERDOC TOOLS

READ 35 tools

Read analyze_bandwidth analyze_bandwidth Read analyze_overdraw analyze_overdraw Read analyze_render_passes Auto-detect render pass boundaries and summarize each pass. Detects passes by Clear actions and ou... Read analyze_state_changes analyze_state_changes Read debug_shader_at_pixel debug_shader_at_pixel Read diagnose_mobile_risks diagnose_mobile_risks Read diagnose_negative_values Scan all float render targets for negative/NaN/Inf pixels and trace their origin. Automatically id... Read diagnose_precision_issues diagnose_precision_issues Read diagnose_reflection_mismatch diagnose_reflection_mismatch Read diff_draw_calls Compare two draw calls and return their state differences. Useful for understanding what changed b... Read disassemble_shader Disassemble the shader bound at the specified stage. If target is omitted, tries all available tar... Read find_draws Search draw calls by rendering state filters. Iterates through draw calls checking pipeline state.... Read get_action Get detailed information about a specific action/draw call. Args: event_id: The event ... Read get_buffer_data get_buffer_data Read get_capture_info Get information about the currently open capture. Returns API type, file path, action count, textu... Read get_cbuffer_contents get_cbuffer_contents Read get_draw_call_state Get complete draw call state in a single call. Returns action info, blend, depth, stencil, rasteri... Read get_frame_overview Get a frame-level statistics overview of the current capture. Returns action counts by type, textu... Read get_pass_timing get_pass_timing Read get_pipeline_state Get the full graphics pipeline state at the current or specified event. Returns topology, viewport... Read get_post_vs_data get_post_vs_data Read get_resource_usage Get the usage history of a resource across all events. Shows which events read from or write to th... Read get_shader_bindings Get resource bindings for a specific shader stage at the current event. Shows constant buffers, sh... Read get_shader_reflection Get reflection information for the shader at the specified stage. Returns input/output signatures,... Read get_texture_stats Get min/max/average statistics for a texture at the current event. Args: resource_id: ... Read get_vertex_inputs Get vertex input layout and buffer bindings at the current event. Shows vertex attributes (name, f... Read list_actions list_actions Read list_buffers List all buffers in the capture. Args: min_size: Optional minimum byte size to filter by. Read list_resources list_resources Read list_textures list_textures Read pick_pixel Get the RGBA value of a specific pixel in a texture. Args: resource_id: The texture re... Read pixel_history Get the full modification history of a pixel across all events in the frame. Shows every event tha... Read read_texture_pixels Read actual pixel values from a rectangular region of a texture. Returns float RGBA values for eac... Read sample_pixel_region sample_pixel_region Read search_actions Search for actions by name pattern and/or flags. Args: name_pattern: Regex pattern to ...

WRITE 5 tools

Write close_capture Close the currently open capture file and free resources. Write export_draw_textures Batch export all textures bound to a draw call's pixel shader. Args: event_id: The eve... Write export_mesh Export mesh data from a draw call as OBJ format. Uses post-vertex-shader data to get transformed p... Write save_render_target Save the current render target(s) at a specific event. Args: event_id: The event ID to... Write save_texture Save a texture resource to an image file. Args: resource_id: The texture resource ID s...

EXECUTE 2 tools

Execute open_capture Open a RenderDoc capture (.rdc) file for analysis. Automatically closes any previously opened capt... Execute set_event Navigate the replay to a specific event ID. This must be called before inspecting pipeline state, ...

// FAQ

How many tools does the Renderdoc MCP server have? +

The Renderdoc MCP server exposes 42 tools across 3 categories: Read, Write, Execute.

How do I enforce policies on Renderdoc tools? +

Route the Renderdoc server through the PolicyLayer gateway. Define allow, deny, or approval rules per tool in the dashboard; they are enforced on every call before it reaches the server.

What risk categories do Renderdoc tools fall into? +

Renderdoc tools are categorised as Read (35), Write (5), Execute (2). Each category has a recommended default policy.

Enforce policy on every Renderdoc tool call.

Start from Renderdoc, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →

Free to start. No card required.

43,000+ MCP servers and 220,000+ tools scanned and risk-classified.