Get the full graphics pipeline state at the current or specified event. Returns topology, viewports, scissors, rasterizer, blend, depth, stencil state, bound shaders, and output targets. Args: event_id: Optional event ID to navigate to first. Uses current event if omitted.
AI agents call get_pipeline_state 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 tool purely queries and retrieves information about the current GPU graphics pipeline state at a specified event. It performs introspection and analysis of existing frame capture data without creating, modifying, deleting, or executing operations. The optional event_id parameter allows navigation but does not alter state.
From the tool's definition Tool description states it 'Get[s] the full graphics pipeline state' and 'Returns topology, viewports, scissors, rasterizer, blend, depth, stencil state, bound shaders, and output targets.' The verb 'Get' and 'Returns' indicate data retrieval with no…
Documented attack patterns abuse exactly the kind of access get_pipeline_state 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_pipeline_state:
{
"version": "1",
"default": "deny",
"tools": {
"get_pipeline_state": {}
}
}get_pipeline_state 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 the full graphics pipeline state at the current or specified event. Returns topology, viewports, scissors, rasterizer, blend, depth, stencil state, bound shaders, and output targets. Args: event_id: Optional event ID to navigate to first. Uses current event if omitted. 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_pipeline_state: 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_pipeline_state 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_pipeline_state 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_pipeline_state. 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_pipeline_state 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.