Get the full SceneConfig JSON schema — all fields, types, enums, and defaults.
AI agents call vitrine_config_schema 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 query to retrieve schema information. It does not modify, execute, delete, or create any data. The confidence is high because the description is clear and unambiguous about its retrieval-only nature. Severity is low because exposure of a schema definition poses minimal risk; it is non-sensitive metadata that aids in understanding API capabilities without enabling harmful actions.
From the tool's definition Tool description explicitly states 'Get the full SceneConfig JSON schema' — a retrieval operation that returns schema metadata with no side effects or data modification.
Attacks that exploit this kind of access
Get the full SceneConfig JSON schema — all fields, types, enums, and defaults. 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_config_schema: 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_config_schema 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_config_schema 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_config_schema. 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_config_schema 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 →