ncbi-eutils.taxonomy.lineage
Get the full taxonomic classification tree for one NCBI TaxID — every ancestor rank from domain/kingdom down to the organism itself (e.g. Eukaryota > Metazoa > Chordata > Mammalia > Carnivora > Felidae > Panthera > Panthera leo), plus scientific name, common name, and parent TaxID. Use ncbi-eutil...
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/ncbi-eutils.taxonomy.lineage.md
What ncbi-eutils.taxonomy.lineage does on Apibase
AI agents call ncbi-eutils.taxonomy.lineage 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 |
|---|---|---|---|
tax_id | string | Yes | NCBI Taxonomy ID (e.g. "9689" for Panthera leo), from ncbi-eutils.taxonomy_search results |
Parameters from the server's own tool schema.
Why ncbi-eutils.taxonomy.lineage is rated Low
Retrieves publicly available taxonomic data from NCBI with no side effects or modifications.
From the tool's definition Get the full taxonomic classification tree, no auth required, eutils.ncbi.nlm.nih.gov
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs ncbi-eutils.taxonomy.lineage 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 ncbi-eutils.taxonomy.lineage, this is the rule to start with:
ncbi-eutils.taxonomy.lineage 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 ncbi-eutils.taxonomy.lineage call is checked against it from then on.
Questions about ncbi-eutils.taxonomy.lineage
Get the full taxonomic classification tree for one NCBI TaxID — every ancestor rank from domain/kingdom down to the organism itself (e.g. Eukaryota > Metazoa > Chordata > Mammalia > Carnivora > Felidae > Panthera > Panthera leo), plus scientific name, common name, and parent TaxID. Use ncbi-eutils.taxonomy_search first to find a tax_id. Data: eutils.ncbi.nlm.nih.gov, no auth required. It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
ncbi-eutils.taxonomy.lineage accepts 1 parameter: tax_id. Required: tax_id. 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 ncbi-eutils.taxonomy.lineage: 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.
ncbi-eutils.taxonomy.lineage 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 ncbi-eutils.taxonomy.lineage 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 ncbi-eutils.taxonomy.lineage. 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.
ncbi-eutils.taxonomy.lineage 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