Batch export all textures bound to a draw call's pixel shader. Args: event_id: The event ID of the draw call. output_dir: Directory to save exported textures. skip_small: Skip textures 4x4 or smaller (placeholder textures). Default True.
AI agents use export_draw_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.
This tool retrieves texture data from a GPU frame capture and writes it to disk as files. While it modifies the local file system by creating new files, it is reversible (files can be deleted) and has no destructive impact on the original capture or system state. The operation is read-like in nature (extracting data from an existing capture) but the file-writing aspect elevates it to Write rather than Read.
From the tool's definition Tool exports and saves textures to disk ("Batch export all textures... output_dir: Directory to save exported textures"), which creates files on the file system.
Documented attack patterns abuse exactly the kind of access export_draw_textures gives an agent:
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 export_draw_textures:
{
"version": "1",
"default": "deny",
"tools": {
"export_draw_textures": {
"limits": [
{
"counter": "export_draw_textures_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}export_draw_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.
Free to start. No card required.
Batch export all textures bound to a draw call's pixel shader. Args: event_id: The event ID of the draw call. output_dir: Directory to save exported textures. skip_small: Skip textures 4x4 or smaller (placeholder textures). Default True. 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.
Register the Renderdoc MCP server in PolicyLayer and add a rule for export_draw_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.
export_draw_textures is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the export_draw_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.
Set action: deny in the PolicyLayer policy for export_draw_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.
export_draw_textures 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.
Start from Renderdoc, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
42 Renderdoc tools catalogued and risk-classified — across an index of 43,000+ MCP servers.