close_capture

THE RISK

Medium Risk

Why close_capture needs a policy

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. The severity is low because the effect is entirely reversible (the file can simply be reopened), and there is minimal blast radius if misused by an AI agent—it would only affect the current debugging session.

From the tool's definition The tool description states it will 'Close the currently open capture file and free resources.' Closing a file is a state-modifying operation, but it does not delete data irreversibly—the capture file itself remains on disk.

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

POLICY

How to control close_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 close_capture:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "close_capture": {
      "limits": [
        {
          "counter": "close_capture_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

close_capture stays usable, but capped — an agent stuck in a loop can't make hundreds of changes 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.

LIMIT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Renderdoc tools

Execute open_capture Open a RenderDoc capture (.rdc) file for analysis. Automatically closes any previ Execute set_event Navigate the replay to a specific event ID. This must be called before inspecting 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 →

Write tools on other servers

M-Team MCP Server download_torrent YouTube MCP Server generate_video_title Android Forensics ADB MCP Server combine_reports 0xarchive web3_signup

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Argument validation → Checking tool call arguments against schema and policy before they run.
Scoped token → Per-person credentials that grant a defined subset of servers and tools.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about close_capture

What does the close_capture tool do? +

Close the currently open capture file and free resources. It is categorised as a Write tool in the Renderdoc MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on close_capture? +

Register the Renderdoc MCP server in PolicyLayer and add a rule for close_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 close_capture? +

close_capture is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit close_capture? +

Yes. Add a rate_limit block to the close_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 close_capture completely? +

Set action: deny in the PolicyLayer policy for close_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 close_capture? +

close_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 →