Upload a GLB/glTF file to Vitrine. Provide the absolute file path on disk.
AI agents use vitrine_upload_model to create or update resources in Vitrine MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Vitrine MCP Server environment.
The upload operation creates or adds data to Vitrine's system reversibly. While uploads can be problematic if an AI agent uploads malicious or unwanted models, this is a Write operation (not Execute, as it doesn't run code; not Destructive, as uploads are reversible; not Financial).
From the tool's definition Tool description states 'Upload a GLB/glTF file to Vitrine' — this creates new data (3D model assets) in the platform that can be modified or removed later.
Attacks that exploit this kind of access
Upload a GLB/glTF file to Vitrine. Provide the absolute file path on disk. It is categorised as a Write tool in the Vitrine MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Vitrine MCP Server MCP server in PolicyLayer and add a rule for vitrine_upload_model: 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 Vitrine MCP Server. Nothing to install.
vitrine_upload_model 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 vitrine_upload_model 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 vitrine_upload_model. 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.
vitrine_upload_model is provided by the Vitrine MCP Server MCP server (vitrine3d/mcp). 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 →