mygene.genes.batch
Retrieve annotation data for up to 1000 genes in a single request by providing a comma-separated list of NCBI Entrez Gene IDs or Ensembl gene IDs. Returns the same fields as mygene.genes.info for each gene: symbol, name, gene type, taxon, summary, Ensembl IDs, UniProt accession, genomic coordinat...
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/mygene.genes.batch.md
What mygene.genes.batch does on Apibase
AI agents call mygene.genes.batch 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 |
|---|---|---|---|
ids | string | Yes | Comma-separated list of NCBI Entrez Gene IDs or Ensembl gene IDs to retrieve in one request (e.g. "1017,1018,1019" for CDK2/CDK3/CDK4, or "ENSG00000123374,ENSG0 |
fields | string | — | Comma-separated fields to return for each gene. Default: symbol, name, taxid, entrezgene, type_of_gene, summary, ensembl, uniprot, alias, genomic_pos, pathway. |
Parameters from the server's own tool schema.
Why mygene.genes.batch is rated Low
Tool queries public genomic databases and returns structured annotation data without modification or side effects.
From the tool's definition Retrieve annotation data, returns fields, gene information lookup
Attacks that exploit this kind of access
The rule that runs mygene.genes.batch 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 mygene.genes.batch, this is the rule to start with:
mygene.genes.batch 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 mygene.genes.batch call is checked against it from then on.
Questions about mygene.genes.batch
Retrieve annotation data for up to 1000 genes in a single request by providing a comma-separated list of NCBI Entrez Gene IDs or Ensembl gene IDs. Returns the same fields as mygene.genes.info for each gene: symbol, name, gene type, taxon, summary, Ensembl IDs, UniProt accession, genomic coordinates, and pathway memberships. Ideal for enriching gene lists from RNA-seq experiments, GWAS results, or drug target panels. Mix of NCBI Entrez and Ensembl IDs is supported in the same request. It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
mygene.genes.batch accepts 2 parameters: ids, fields. Required: ids. 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 mygene.genes.batch: 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.
mygene.genes.batch 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 mygene.genes.batch 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 mygene.genes.batch. 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.
mygene.genes.batch 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