Call this before finalizing generated or user-written Vlossom code. Validates SFCs, snippets, StyleSet objects, and project setup against Vlossom metadata for the requested version. Detects empty input as skipped, unknown components, prop/slot/event/v-model mistakes, setup issues, and default Vlo...
AI agents call validate_vlossom_usage to retrieve information from Vlossom without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
code | string | — | |
kind | string | Yes | |
mode | string | — | |
files | array | — | |
context | object | — | |
packageJson | string | — |
Parameters from the server's own tool schema.
Even though validate_vlossom_usage only reads data, uncontrolled read access leaks sensitive information and racks up API costs — an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Risk signalsAccepts freeform code/query input (code) · Accepts file system path (files[].path) · Accepts raw HTML/template content (files[].content) · High parameter count (13 properties)
Attacks that exploit this kind of access
Call this before finalizing generated or user-written Vlossom code. Validates SFCs, snippets, StyleSet objects, and project setup against Vlossom metadata for the requested version. Detects empty input as skipped, unknown components, prop/slot/event/v-model mistakes, setup issues, and default Vlossom-first violations with explicit opt-out support. Then fix violations using get_vlossom_reference or scaffold_vlossom_code and validate again. It is categorised as a Read tool in the Vlossom MCP Server, which means it retrieves data without modifying state.
validate_vlossom_usage accepts 6 parameters: code, kind, mode, files, context, packageJson. Required: kind. The full parameter table on this page comes from the server's own tool schema.
Register the Vlossom MCP server in PolicyLayer and add a rule for validate_vlossom_usage: 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 Vlossom. Nothing to install.
validate_vlossom_usage 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 validate_vlossom_usage 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 validate_vlossom_usage. 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.
validate_vlossom_usage is provided by the Vlossom MCP server (vlossom-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.