Get resource bindings for a specific shader stage at the current event. Shows constant buffers, shader resource views (SRVs), UAVs, and samplers. Args: stage: Shader stage name (vertex, hull, domain, geometry, pixel, compute). event_id: Optional event ID to navigate to first.
AI agents call get_shader_bindings to retrieve information from Renderdoc without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a pure read operation that queries and returns shader binding information from an already-loaded RenderDoc frame capture. It does not modify state, execute arbitrary code, delete data, or commit financial transactions. The most severe risk is that an agent might query sensitive shader constants, but this is limited to already-captured frame data and poses minimal blast radius.
From the tool's definition The tool retrieves resource bindings for a specific shader stage, showing constant buffers, SRVs, UAVs, and samplers. The verb 'Get' and description 'Shows' indicate data retrieval with no modification or side effects.
Documented attack patterns abuse exactly the kind of access get_shader_bindings 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 get_shader_bindings:
{
"version": "1",
"default": "deny",
"tools": {
"get_shader_bindings": {}
}
}get_shader_bindings is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get resource bindings for a specific shader stage at the current event. Shows constant buffers, shader resource views (SRVs), UAVs, and samplers. Args: stage: Shader stage name (vertex, hull, domain, geometry, pixel, compute). event_id: Optional event ID to navigate to first. It is categorised as a Read tool in the Renderdoc MCP Server, which means it retrieves data without modifying state.
Register the Renderdoc MCP server in PolicyLayer and add a rule for get_shader_bindings: 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.
get_shader_bindings is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_shader_bindings 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 get_shader_bindings. 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.
get_shader_bindings 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.