Export mesh data from a draw call as OBJ format. Uses post-vertex-shader data to get transformed positions, normals, and UVs. Args: event_id: The event ID of the draw call. output_path: Output file path for the .obj file.
AI agents use export_mesh 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 creates/writes a file to disk (export_mesh writing OBJ format to output_path), which is a reversible modification action. It does not execute arbitrary code, delete data, or modify the GPU capture itself—it only exports derived data from an already-loaded capture for analysis.
From the tool's definition Tool exports mesh data and writes to a file ('output_path': Output file path for the .obj file). The action creates a new file with exported graphics data.
Documented attack patterns abuse exactly the kind of access export_mesh 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_mesh:
{
"version": "1",
"default": "deny",
"tools": {
"export_mesh": {
"limits": [
{
"counter": "export_mesh_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}export_mesh 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.
Export mesh data from a draw call as OBJ format. Uses post-vertex-shader data to get transformed positions, normals, and UVs. Args: event_id: The event ID of the draw call. output_path: Output file path for the .obj file. 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_mesh: 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_mesh 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_mesh 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_mesh. 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_mesh 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.