myvariant.variants.metadata
Retrieve build metadata and data source statistics for the MyVariant.info API. Returns the current database build version (e.g. "20250624"), build date, total number of variant records, and a list of integrated annotation sources with their versions, URLs, and license information. Sources include...
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/myvariant.variants.metadata.md
What myvariant.variants.metadata does on Apibase
AI agents call myvariant.variants.metadata to retrieve information from Apibase without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
detail | boolean | — | If true, include full source metadata (download dates, record counts per source, code repository links). If false (default), return only build version, build da |
Parameters from the server's own tool schema.
Why myvariant.variants.metadata is rated Low
Read-only retrieval of metadata and version information; no side effects.
From the tool's definition Retrieve build metadata and data source statistics
Attacks that exploit this kind of access
The rule that runs myvariant.variants.metadata safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Apibase, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For myvariant.variants.metadata, this is the rule to start with:
myvariant.variants.metadata is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Apibase, apply this rule, and every myvariant.variants.metadata call is checked against it from then on.
Questions about myvariant.variants.metadata
Retrieve build metadata and data source statistics for the MyVariant.info API. Returns the current database build version (e.g. "20250624"), build date, total number of variant records, and a list of integrated annotation sources with their versions, URLs, and license information. Sources include ClinVar, gnomAD, CADD, dbSNP v156, COSMIC, CIViC, ExAC, GWAS Catalog, SnpEff, EVS, EMV, and 20+ additional variant databases. Use to verify data currency before running large annotation jobs or to cite specific source versions in research. It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
myvariant.variants.metadata accepts 1 parameter: detail. The full parameter table on this page comes from the server's own tool schema.
Register the Apibase MCP server in PolicyLayer and add a rule for myvariant.variants.metadata: 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 Apibase. Nothing to install.
myvariant.variants.metadata 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 myvariant.variants.metadata 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 myvariant.variants.metadata. 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.
myvariant.variants.metadata is provided by the Apibase MCP server (apibase-mcp-client). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Apibase, and thousands of servers like it.
This server
Across the catalogue