blender_log_stats
Get statistics about current log buffer.
This record as markdown: /tools/sandraschi-blender-mcp/blender-log-stats.md
What blender_log_stats does on Blender
AI agents call blender_log_stats to retrieve information from Blender without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why blender_log_stats is rated Low
This tool retrieves and reports statistics about an existing log buffer. It performs a read-only operation with no ability to modify, delete, execute commands, or affect financial systems. The blast radius of misuse is minimal—an agent could at most spam queries or consume compute resources viewing logs. This is a straightforward Read operation typical of logging/monitoring tools.
From the tool's definition Tool name 'blender_log_stats' and description 'Get statistics about current log buffer' indicate a retrieval operation that queries log data without modification or side effects.
Attacks that exploit this kind of access
The rule that runs blender_log_stats safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Blender, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For blender_log_stats, this is the rule to start with:
blender_log_stats is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Blender, apply this rule, and every blender_log_stats call is checked against it from then on.
Questions about blender_log_stats
Get statistics about current log buffer. It is categorised as a Read tool in the Blender MCP Server, which means it retrieves data without modifying state.
Register the Blender MCP server in PolicyLayer and add a rule for blender_log_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 Blender. Nothing to install.
blender_log_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 blender_log_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 blender_log_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.
blender_log_stats is provided by the Blender MCP server (sandraschi/blender-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Blender, and thousands of servers like it.
This server
Across the catalogue