Low Risk

blender_log_stats

Get statistics about current log buffer.

How to control blender_log_stats ↓

What blender_log_stats does on Blender

AI agents call blender_log_stats to retrieve information from Blender without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

Why blender_log_stats needs a policy

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.

Documented attack patterns abuse exactly the kind of access blender_log_stats gives an agent:

How to control blender_log_stats

PolicyLayer is an MCP gateway — it sits between your AI agents and Blender, and nothing reaches the server without passing your rules. This is the rule we recommend for blender_log_stats:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "blender_log_stats": {}
  }
}

blender_log_stats is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Blender — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about blender_log_stats

What does the blender_log_stats tool do? +

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.

How do I enforce a policy on blender_log_stats? +

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.

What risk level is blender_log_stats? +

blender_log_stats is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit blender_log_stats? +

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.

How do I block blender_log_stats completely? +

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.

What MCP server provides blender_log_stats? +

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.

Enforce policy on every Blender tool call.

Start from Blender, 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.

77 Blender tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.