List all your Vitrine 3D models with IDs, names, and publish status.
AI agents call vitrine_list_models to retrieve information from Vitrine MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a read-only operation to enumerate and retrieve metadata about existing 3D models. It has no side effects, creates no data, executes no code, and does not delete or modify resources. The blast radius of misuse is minimal—an AI agent could only retrieve information about the user's models, which is non-destructive.
From the tool's definition Tool name 'vitrine_list_models' combined with description 'List all your Vitrine 3D models with IDs, names, and publish status' indicates a retrieval operation that queries and displays data without modification.
Attacks that exploit this kind of access
List all your Vitrine 3D models with IDs, names, and publish status. It is categorised as a Read tool in the Vitrine MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Vitrine MCP Server MCP server in PolicyLayer and add a rule for vitrine_list_models: 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_list_models is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the vitrine_list_models 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_list_models. 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_list_models 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 →