Look up Blender Python API documentation for an identifier.
AI agents call blender_api_docs 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.
This tool performs read-only documentation lookup. It retrieves and queries reference information about Blender's Python API without creating, modifying, executing code, or causing any irreversible changes. The action is purely informational and carries minimal risk in the context of AI agent misuse.
From the tool's definition Tool description states 'Look up Blender Python API documentation for an identifier' — a straightforward documentation retrieval operation with no side effects.
Documented attack patterns abuse exactly the kind of access blender_api_docs gives an agent:
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_api_docs:
{
"version": "1",
"default": "deny",
"tools": {
"blender_api_docs": {}
}
}blender_api_docs 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.
Look up Blender Python API documentation for an identifier. 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.
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.