Get a frame-level statistics overview of the current capture. Returns action counts by type, texture/buffer memory totals, main render targets with draw counts, and estimated resolution.
AI agents call get_frame_overview 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 retrieves and queries statistical metadata about a GPU frame capture without performing any side effects, modifications, or executing arbitrary code. It is purely an informational tool for graphics debugging analysis. The data returned (counts, totals, resolution estimates) are read-only observations of already-captured frame data. No resources are created, modified, deleted, or executed.
From the tool's definition Tool 'get_frame_overview' returns frame-level statistics overview including action counts, memory totals, and render target information.
Documented attack patterns abuse exactly the kind of access get_frame_overview 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_frame_overview:
{
"version": "1",
"default": "deny",
"tools": {
"get_frame_overview": {}
}
}get_frame_overview 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 a frame-level statistics overview of the current capture. Returns action counts by type, texture/buffer memory totals, main render targets with draw counts, and estimated resolution. 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_frame_overview: 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_frame_overview 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_frame_overview 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_frame_overview. 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_frame_overview 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.