22 tools. 9 can modify or destroy data without limits.
9 write tools that can modify data. Rate limits recommended.
Last updated:
Write operations (download_polyhaven_asset, download_sketchfab_model, generate_hunyuan3d_model) modify state. Without rate limits, an agent can make hundreds of changes in seconds — faster than any human can review or revert.
Execute tools (execute_blender_code) trigger processes with side effects. Builds, notifications, workflows — all fired without throttling.
Intercept sits between your agent and Blender. Every tool call checked against your policy before it executes — so your agent can do its job without breaking things.
npx -y @policylayer/intercept scan -- npx -y @ahujasid/blender-mcp download_polyhaven_asset:
rules:
- rate_limit: 30/hour Prevents bulk unintended modifications from agents caught in loops.
get_hunyuan3d_status:
rules:
- rate_limit: 60/minute Controls API costs and prevents retry loops from exhausting upstream rate limits.
The Blender server has 8 write tools including download_polyhaven_asset, download_sketchfab_model, generate_hunyuan3d_model. Set rate limits in your policy file -- for example, rate_limit: 10/hour prevents an agent from making more than 10 modifications per hour. Intercept enforces this at the transport layer.
22 tools across 3 categories: Execute, Read, Write. 13 are read-only. 9 can modify, create, or delete data.
One line change. Instead of running the Blender server directly, prefix it with Intercept: intercept -c blender.yaml -- npx -y @@ahujasid/blender-mcp. Download a pre-built policy from policylayer.com/policies/blender and adjust the limits to match your use case.
Starter policies available for each. Same risk classification, same one-command setup.
Set budgets, approvals, and hard limits across MCP servers.
npx -y @policylayer/intercept init