// MCP TOOL REFERENCE

open_capture

ServerRenderdoc
CategoryExecute

WHAT IT DOES

What open_capture does on Renderdoc

AI agents invoke open_capture to trigger actions in Renderdoc. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

THE RISK

High Risk

Why open_capture needs a policy

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. It falls under Execute rather than Read because of these side effects. Severity is medium since misuse could disrupt an ongoing analysis session or load an unintended file.

From the tool's definition 'Open a RenderDoc capture (.rdc) file for analysis. Automatically closes any previously opened capture.' — triggers external operation (opening a file in RenderDoc's headless API) with side effects (closing prior capture state).

Documented attack patterns abuse exactly the kind of access open_capture gives an agent:

POLICY

How to control open_capture

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 open_capture:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "open_capture": {
      "limits": [
        {
          "counter": "open_capture_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

open_capture stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

Create a free account and register Renderdoc — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

RATE-LIMIT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Renderdoc tools

Execute set_event Navigate the replay to a specific event ID. This must be called before inspecting 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: Write export_mesh Export mesh data from a draw call as OBJ format. Uses post-vertex-shader data to Write save_render_target Save the current render target(s) at a specific event. Args: event_id Write save_texture Save a texture resource to an image file. Args: resource_id: The text Read analyze_bandwidth analyze_bandwidth Read analyze_overdraw analyze_overdraw

All 42 Renderdoc tools →

Execute tools on other servers

Android Forensics ADB MCP Server adb_shell_command EMBA-MCP run_emba_scan Frida Game Hacking MCP remove_breakpoint Procmon request_elevation

Go deeper

High-risk tools in Renderdoc → Every high-risk tool this server exposes, in one view.
All high-risk MCP tools → Every high-risk tool across the catalogue, and the policy pattern that contains them.
The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Agent sandbox → Bounding what an agent can execute and where the boundary should sit.
Least privilege for MCP → Granting agents the minimum tool surface the task needs.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about open_capture

What does the open_capture tool do? +

Open a RenderDoc capture (.rdc) file for analysis. Automatically closes any previously opened capture. Returns capture overview: API type, action count, resource counts. Args: filepath: Absolute path to the .rdc capture file. It is categorised as a Execute tool in the Renderdoc MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on open_capture? +

Register the Renderdoc MCP server in PolicyLayer and add a rule for open_capture: 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.

What risk level is open_capture? +

open_capture is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit open_capture? +

Yes. Add a rate_limit block to the open_capture 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.

How do I block open_capture completely? +

Set action: deny in the PolicyLayer policy for open_capture. 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.

What MCP server provides open_capture? +

open_capture 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.

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.

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