close_capture · Renderdoc MCP: Risk & Policy

WHAT IT DOES

What close_capture does on Renderdoc

AI agents use close_capture to create or update resources in Renderdoc — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Renderdoc environment.

WHY IT NEEDS A POLICY

Why close_capture needs a policy

Closing a capture is a reversible write operation—it transitions the capture state from open to closed without deleting underlying data or files. The user can reopen the same capture file later. This is distinct from destructive operations (which would delete files) or execute operations (which would run code). The blast radius is minimal since it only affects the current session state with no external side effects.

From the tool's definition Tool description states '关闭当前 capture' (Close the current capture). This is a state modification operation that closes/unloads an open capture session.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

close_capture Rate-limited

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.

View as policy code

policy.json

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

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Renderdoc, so you can run agents against it safely.

FAQ

Questions about close_capture

What does the close_capture tool do? +

关闭当前 capture。. 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 (kenzo1024/renderdocmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.