Get min/max/average statistics for a texture at the current event. Args: resource_id: The texture resource ID string. event_id: Optional event ID to navigate to first. all_slices: If True, return per-slice/per-face statistics. Useful for cubemaps (returns stats for each of the 6 faces) and textur...
AI agents call get_texture_stats 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 only reads and computes statistics (min/max/average) from an existing texture resource in a GPU frame capture. It has no side effects, does not modify any data, and purely retrieves analytical information about texture values.
From the tool's definition Get min/max/average statistics for a texture at the current event
Documented attack patterns abuse exactly the kind of access get_texture_stats 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_texture_stats:
{
"version": "1",
"default": "deny",
"tools": {
"get_texture_stats": {}
}
}get_texture_stats 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 min/max/average statistics for a texture at the current event. Args: resource_id: The texture resource ID string. event_id: Optional event ID to navigate to first. all_slices: If True, return per-slice/per-face statistics. Useful for cubemaps (returns stats for each of the 6 faces) and texture arrays. Default False returns only slice 0. 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_texture_stats: 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_texture_stats 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_texture_stats 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_texture_stats. 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_texture_stats 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.