Get ready-to-paste HTML embed code for a published model.
AI agents call vitrine_get_embed 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 is a retrieval operation that fetches and returns existing HTML embed code. It does not create, modify, delete, or execute anything—it simply queries and returns read-only data for a published model. The data retrieved is intended for public embedding, presenting minimal security risk. Classified as Read with low severity.
From the tool's definition Tool name 'vitrine_get_embed' and description 'Get ready-to-paste HTML embed code for a published model' indicate retrieval of already-published embed code with no modifications or side effects.
Attacks that exploit this kind of access
Get ready-to-paste HTML embed code for a published model. 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_embed: 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_embed 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_embed 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_embed. 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_embed 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 →