Export mesh as VeFrank-compatible asset with metadata
AI agents use export_vefrank_asset to create or update resources in MCP-Blender — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your MCP-Blender environment.
This tool exports/creates a mesh asset in a specific format (VeFrank-compatible) with associated metadata. This is a Write operation because it creates and saves new data files. It is not Execute because it does not run arbitrary code or trigger external processes based on user input (unlike sibling tools like execute_code).
From the tool's definition Tool name 'export_vefrank_asset' and description 'Export mesh as VeFrank-compatible asset with metadata' indicate creation/generation of asset files with metadata.
Attacks that exploit this kind of access
Export mesh as VeFrank-compatible asset with metadata. It is categorised as a Write tool in the MCP-Blender MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the MCP-Blender MCP server in PolicyLayer and add a rule for export_vefrank_asset: 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 MCP-Blender. Nothing to install.
export_vefrank_asset 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 export_vefrank_asset 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 export_vefrank_asset. 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.
export_vefrank_asset is provided by the MCP-Blender MCP server (shdann/mcp-blend). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →