This record as markdown: /tools/sandraschi-blender-mcp/blender-api-docs.md
What blender_api_docs does on Blender
AI agents call blender_api_docs 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_api_docs is rated Low
Based on the name, this tool likely retrieves or queries Blender API documentation. Documentation access is a read-only operation with no side effects on Blender scenes, objects, or data. The empty description reduces confidence slightly, but the naming convention strongly indicates a reference/documentation lookup function rather than any modification or execution capability.
From the tool's definition Tool name 'blender_api_docs' suggests retrieval of documentation or reference materials. Empty description limits certainty.
Attacks that exploit this kind of access
The rule that runs blender_api_docs 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_api_docs, this is the rule to start with:
blender_api_docs 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_api_docs call is checked against it from then on.
Questions about blender_api_docs
blender_api_docs 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_api_docs: 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_api_docs 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_api_docs 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_api_docs. 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_api_docs 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