This record as markdown: /tools/sandraschi-blender-mcp/blender-view-logs.md
What blender_view_logs does on Blender
AI agents call blender_view_logs 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_view_logs is rated Low
Viewing logs is a read operation that retrieves diagnostic or operational information without modifying, executing, or destroying data. The empty description lowers confidence slightly, but the tool name strongly suggests passive inspection of log files rather than any state-changing operation.
From the tool's definition Tool name 'blender_view_logs' indicates retrieval of log data for viewing/inspection purposes. No description provided, but naming convention suggests read-only access to existing logs.
Attacks that exploit this kind of access
The rule that runs blender_view_logs 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_view_logs, this is the rule to start with:
blender_view_logs 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_view_logs call is checked against it from then on.
Questions about blender_view_logs
blender_view_logs is a read tool on the Blender MCP server. 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_view_logs: 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_view_logs 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_view_logs 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_view_logs. 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_view_logs 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