Call this after search_vlossom returns a registry-backed id or when the user asks for exact Vlossom APIs. Returns source-of-truth component metadata, GitHub-backed source, relationships, directives, composables, tokens, options, changelog, or rules. Component API data comes from the GitHub regist...
AI agents call get_vlossom_reference 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 |
|---|---|---|---|
id | string | — | |
type | string | Yes | |
include | array | — | |
version | string | — | |
language | string | — | |
packageJson | string | — |
Parameters from the server's own tool schema.
Even though get_vlossom_reference 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.
Attacks that exploit this kind of access
Call this after search_vlossom returns a registry-backed id or when the user asks for exact Vlossom APIs. Returns source-of-truth component metadata, GitHub-backed source, relationships, directives, composables, tokens, options, changelog, or rules. Component API data comes from the GitHub registry for the requested version and source is fetched only when requested. Then use scaffold_vlossom_code or validate_vlossom_usage with the returned exact API. It is categorised as a Read tool in the Vlossom MCP Server, which means it retrieves data without modifying state.
get_vlossom_reference accepts 6 parameters: id, type, include, version, language, packageJson. Required: type. 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 get_vlossom_reference: 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.
get_vlossom_reference 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 get_vlossom_reference 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 get_vlossom_reference. 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.
get_vlossom_reference 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.