Get the full merged scene config for a model (look + layout + overrides).
AI agents call vitrine_get_config 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 retrieves configuration data for a 3D model scene without modifying, deleting, or executing anything. It is a query operation that returns existing configuration (merged from look + layout + overrides). No data is created, modified, deleted, or executed. The blast radius if misused is minimal—an agent could only access configuration details of existing scenes.
From the tool's definition Tool name 'vitrine_get_config' with description 'Get the full merged scene config for a model'. The verb 'Get' and action of retrieving/querying configuration data indicates a read-only operation with no side effects.
Attacks that exploit this kind of access
Get the full merged scene config for a model (look + layout + overrides). 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_get_config: 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_get_config 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_get_config 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_get_config. 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_get_config 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 →