blender_grease_pencil
AI agents call blender_grease_pencil as a supporting operation in Blender workflows.
The description is empty and uninformative. The name suggests interaction with Blender's Grease Pencil system, which could involve reading, writing, or executing operations. Given the server context of AI-powered Blender control, it likely writes or modifies Grease Pencil strokes/objects, but without a description, confidence is low. Defaulting to Other with lowered confidence as per rules.
From the tool's definition Tool name 'blender_grease_pencil' and empty description provide no detail on what the tool does beyond referencing Blender's Grease Pencil feature (2D/3D drawing/annotation tool).
Documented attack patterns abuse exactly the kind of access blender_grease_pencil 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_grease_pencil:
{
"version": "1",
"default": "deny",
"tools": {
"blender_grease_pencil": {
"limits": [
{
"counter": "blender_grease_pencil_rate",
"window": "minute",
"max": 60,
"scope": "grant"
}
]
}
}
} blender_grease_pencil gets a rate cap, and everything else on the server is denied unless you say otherwise.
Free to start. No card required.
blender_grease_pencil. 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 blender_grease_pencil: 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_grease_pencil 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 blender_grease_pencil 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_grease_pencil. 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_grease_pencil 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.