Search aggregated human genetic-variant annotations on MyVariant.info. Accepts an rsID ("rs58991260"), an HGVS id ("chr1:g.218631822G>A"), or a fielded query ("dbnsfp.genename:CDK2", "clinvar.rcv.clinical_significance:pathogenic"). Each hit merges dbSNP, ClinVar clinical significance, CADD/dbNSFP...
AI agents call query to retrieve information from Mcp Myvariant without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
size | number | — | Max hits to return, 1-1000 (default 10). |
query | string | Yes | rsID, HGVS id, or fielded query. e.g. "rs58991260", "chr1:g.218631822G>A", "dbnsfp.genename:CDK2". |
fields | string | — | Comma-separated return fields (default: all). e.g. "dbsnp,clinvar,cadd.phred,gnomad_genome.af". |
Parameters from the server's own tool schema.
This tool retrieves and queries genetic variant metadata from MyVariant.info without side effects. It searches across multiple annotation sources (dbSNP, ClinVar, CADD, gnomAD) and returns results. There is no indication of data creation, modification, deletion, code execution, or financial operations. The tool is read-only and classified as a simple data lookup/retrieval operation.
From the tool's definition Tool accepts rsID, HGVS id, or fielded query parameters and "Returns { total, hits }" with aggregated annotations. No modification of data described; core action is 'Search' and 'provides' data retrieval.
Risk signalsAccepts freeform code/query input (query)
Attacks that exploit this kind of access
Search aggregated human genetic-variant annotations on MyVariant.info. Accepts an rsID ("rs58991260"), an HGVS id ("chr1:g.218631822G>A"), or a fielded query ("dbnsfp.genename:CDK2", "clinvar.rcv.clinical_significance:pathogenic"). Each hit merges dbSNP, ClinVar clinical significance, CADD/dbNSFP deleteriousness scores, and gnomAD population allele frequencies. Returns { total, hits }; hit._id is usually the HGVS id you can pass to the variant tool. It is categorised as a Read tool in the Mcp Myvariant MCP Server, which means it retrieves data without modifying state.
query accepts 3 parameters: size, query, fields. Required: query. The full parameter table on this page comes from the server's own tool schema.
Register the Mcp Myvariant MCP server in PolicyLayer and add a rule for query: 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 Mcp Myvariant. Nothing to install.
query 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 query 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 query. 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.
query is provided by the Mcp Myvariant MCP server (https://gateway.pipeworx.io/myvariant/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 →