Apply a Look preset to a model by setting its look_id.
AI agents use vitrine_apply_look 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.
This tool creates or updates model state by applying a preset configuration, which is characteristic of Write category operations. Severity is medium because the modification is reversible (another look can be applied) and affects only visual presentation rather than infrastructure or data deletion.
From the tool's definition The tool description states it 'Apply[s] a Look preset to a model by setting its look_id,' which modifies the visual configuration (look_id) of an existing model. This is a data modification operation that changes model state.
Attacks that exploit this kind of access
Apply a Look preset to a model by setting its look_id. 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_apply_look: 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_apply_look 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_apply_look 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_apply_look. 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_apply_look 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 →