export_event_textures · Renderdoc MCP: Risk & Policy

WHAT IT DOES

What export_event_textures does on Renderdoc

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

The tool exports texture data from GPU frame captures, which creates new files or data outputs. This is a Write operation (creates/outputs data) rather than Read (which would only retrieve metadata).

From the tool's definition Tool name 'export_event_textures' and description '导出一个 draw 绑定的纹理' (export textures bound to a draw event) indicate the tool writes/exports texture data to files or external storage.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

export_event_textures Rate-limited

export_event_textures 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": {
    "export_event_textures": {
      "limits": [
        {
          "counter": "export_event_textures_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 export_event_textures

What does the export_event_textures tool do? +

导出一个 draw 绑定的纹理。. 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 export_event_textures? +

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

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

Can I rate-limit export_event_textures? +

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

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

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