blender_vrm_metadata
AI agents use blender_vrm_metadata to create or update resources in Blender — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Blender environment.
Based on the tool name and server context, this tool likely creates or modifies VRM metadata (character/model information), which is a reversible write operation. VRM metadata can include avatar properties, skeletal information, and material assignments. This is categorized as Write rather than Execute because it operates on data structures rather than executing arbitrary code or scripts.
From the tool's definition Tool name 'blender_vrm_metadata' suggests metadata modification for VRM (Virtual Reality Model) files. VRM is a 3D model format commonly used for avatars.
Documented attack patterns abuse exactly the kind of access blender_vrm_metadata 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_vrm_metadata:
{
"version": "1",
"default": "deny",
"tools": {
"blender_vrm_metadata": {
"limits": [
{
"counter": "blender_vrm_metadata_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}blender_vrm_metadata stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
blender_vrm_metadata. It is categorised as a Write tool in the Blender MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Blender MCP server in PolicyLayer and add a rule for blender_vrm_metadata: 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_vrm_metadata is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the blender_vrm_metadata 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_vrm_metadata. 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_vrm_metadata 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.