// SCAN REPORT

Renderdoc

42 tools. 7 can modify or destroy data without limits.

7 write tools that can modify data. Rate limits recommended.

Last updated: 11 Jun 2026

7 can modify or destroy data

35 read-only

42 tools total

Community server · catalogue entry verified 11/06/2026

How to control Renderdoc ↓

TOOL MAP

What Renderdoc exposes to your agents

Read (35) Write / Execute (7) Destructive / Financial (0)

Running more than one server? Check your whole stack →

MOST DANGEROUS TOOLS

High Risk

The most dangerous Renderdoc tools

Execute · Medium open_capture This tool does more than a passive read; it triggers an external operation by loading a file into the RenderDoc API and implicitly closes any previously opened capture, altering application state. Execute · Medium set_event This tool actively changes the state of the RenderDoc replay session by navigating to a specific event, which affects all subsequent operations. Write · Low close_capture This is a Write-category operation because it modifies the current state (closing/releasing the open capture), but it is not Destructive since the underlying capture file persists and can be reopened. Write · Low export_draw_textures This tool retrieves texture data from a GPU frame capture and writes it to disk as files.

7 of Renderdoc's 42 tools can modify, destroy, or commit something on every call — and an agent calls them with no built-in limits.

POLICY

How to control Renderdoc

PolicyLayer is an MCP gateway — it sits between your AI agents and Renderdoc, and nothing reaches the server without passing your rules. These are the rules we recommend:

Rate limit write operations

{
  "close_capture": {
    "limits": [
      {
        "counter": "close_capture_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations

{
  "analyze_bandwidth": {
    "limits": [
      {
        "counter": "analyze_bandwidth_per_minute",
        "window": "minute",
        "max": 60,
        "scope": "grant"
      }
    ]
  }
}

Controls API costs and prevents retry loops from exhausting upstream rate limits.

Create a free account and register Renderdoc — nothing to install.
Add these rules — paste them, or build them visually. Tune the limits to your setup.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

ENFORCE POLICY ON RENDERDOC →

Free to start. No card required.

FULL CATALOGUE

All 42 Renderdoc tools

EXECUTE 2 tools

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

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 event Write export_mesh Export mesh data from a draw call as OBJ format. Uses post-vertex-shader data to get transformed posi Write save_render_target Save the current render target(s) at a specific event. Args: event_id: The event ID to ca Write save_texture Save a texture resource to an image file. Args: resource_id: The texture resource ID stri

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 outpu 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 ident 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 betw Read disassemble_shader Disassemble the shader bound at the specified stage. If target is omitted, tries all available target Read find_draws Search draw calls by rendering state filters. Iterates through draw calls checking pipeline state. Th Read get_action Get detailed information about a specific action/draw call. Args: event_id: The event ID 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, texture/ 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, rasterizer Read get_frame_overview Get a frame-level statistics overview of the current capture. Returns action counts by type, texture/ 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, viewports, 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 this Read get_shader_bindings Get resource bindings for a specific shader stage at the current event. Shows constant buffers, shade Read get_shader_reflection Get reflection information for the shader at the specified stage. Returns input/output signatures, co Read get_texture_stats Get min/max/average statistics for a texture at the current event. Args: resource_id: The Read get_vertex_inputs Get vertex input layout and buffer bindings at the current event. Shows vertex attributes (name, form 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 resou Read pixel_history Get the full modification history of a pixel across all events in the frame. Shows every event that w Read read_texture_pixels Read actual pixel values from a rectangular region of a texture. Returns float RGBA values for each p 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 mat

FAQ

Questions about Renderdoc

How do I prevent bulk modifications through Renderdoc? +

The Renderdoc server has 5 write tools including close_capture, export_draw_textures, export_mesh. Set a rate limit in your policy -- for example, 10 calls per hour prevents an agent from making more than 10 modifications per hour. PolicyLayer enforces this at the gateway, before calls reach Renderdoc.

How many tools does the Renderdoc MCP server expose? +

42 tools across 2 categories: Read, Write. 35 are read-only. 7 can modify, create, or delete data.

How do I enforce a policy on Renderdoc? +

Register the Renderdoc MCP server in PolicyLayer, apply the suggested rules above (adjust the limits to your use case), and point your AI client at the PolicyLayer proxy URL instead of the server directly. Your agents keep the same tools; PolicyLayer evaluates every call against policy before it executes. Nothing to install, live in minutes.

Enforce policy on every Renderdoc tool call.

Deterministic rules across all 42 Renderdoc tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

ENFORCE POLICY ON RENDERDOC →

Free to start. No card required.

42 Renderdoc tools catalogued and risk-classified — across an index of 43,000+ MCP servers.