conversational_blender_assistant
AI agents call conversational_blender_assistant as a supporting operation in Blender workflows.
The description is empty, providing no information about what this tool actually does. The name suggests a conversational interface, which could be read-only (answering questions) or could trigger other operations. Given the sibling tools on this server (which include execute, write, and destructive operations), this assistant could potentially orchestrate any of them, but without evidence we cannot assume the worst.
From the tool's definition Tool name is 'conversational_blender_assistant' with empty description.
Documented attack patterns abuse exactly the kind of access conversational_blender_assistant 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 conversational_blender_assistant:
{
"version": "1",
"default": "deny",
"tools": {
"conversational_blender_assistant": {
"limits": [
{
"counter": "conversational_blender_assistant_rate",
"window": "minute",
"max": 60,
"scope": "grant"
}
]
}
}
} conversational_blender_assistant gets a rate cap, and everything else on the server is denied unless you say otherwise.
Free to start. No card required.
conversational_blender_assistant. It is categorised as a Other tool in the Blender MCP Server, which means it performs auxiliary operations.
Register the Blender MCP server in PolicyLayer and add a rule for conversational_blender_assistant: 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.
conversational_blender_assistant is a Other tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the conversational_blender_assistant 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 conversational_blender_assistant. 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.
conversational_blender_assistant 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.