connect_to_gui_capture · Renderdoc MCP: Risk & Policy

WHAT IT DOES

What connect_to_gui_capture does on Renderdoc

AI agents use connect_to_gui_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 connect_to_gui_capture needs a policy

An AI agent can call connect_to_gui_capture faster than any human can review — one bad instruction and it creates or modifies resources in Renderdoc by the hundred, each call as confident as the last.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

connect_to_gui_capture Rate-limited

connect_to_gui_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": {
    "connect_to_gui_capture": {
      "limits": [
        {
          "counter": "connect_to_gui_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 connect_to_gui_capture

What does the connect_to_gui_capture tool do? +

打开 RenderDoc GUI 当前加载的 rdc。. 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 connect_to_gui_capture? +

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

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

Can I rate-limit connect_to_gui_capture? +

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

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

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

// THE FULL RECORD

connect_to_gui_capture is one line of Renderdoc's registry record.

The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.

Teams ship this data inside their own products. See what a licence covers →