ebi-metagenomics.biomes.browse
Browse MGnify's environment classification tree starting at a given lineage — returns the queried biome plus every descendant beneath it (not just immediate children), e.g. lineage "root" for the entire tree or "root:Host-associated" for just that subtree. Returns each biome's lineage, name, and ...
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/ebi-metagenomics.biomes.browse.md
What ebi-metagenomics.biomes.browse does on Apibase
AI agents call ebi-metagenomics.biomes.browse 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 |
|---|---|---|---|
page | integer | — | Page number, 1-indexed (default 1). |
lineage | string | — | Biome lineage to browse the descendant subtree of, e.g. "root" (entire tree), "root:Host-associated", or "root:Environmental:Aquatic:Marine". Defaults to "root" |
page_size | integer | — | Number of biomes to return per page, 1-50 (default 20). |
Parameters from the server's own tool schema.
Why ebi-metagenomics.biomes.browse is rated Low
Queries hierarchical biome data without modifying, deleting, or executing operations.
From the tool's definition Browse, returns biome classification tree, no auth required, no side effects.
Risk signalsAdmin/system-level operation
Attacks that exploit this kind of access
The rule that runs ebi-metagenomics.biomes.browse 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 ebi-metagenomics.biomes.browse, this is the rule to start with:
ebi-metagenomics.biomes.browse 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 ebi-metagenomics.biomes.browse call is checked against it from then on.
Questions about ebi-metagenomics.biomes.browse
Browse MGnify's environment classification tree starting at a given lineage — returns the queried biome plus every descendant beneath it (not just immediate children), e.g. lineage "root" for the entire tree or "root:Host-associated" for just that subtree. Returns each biome's lineage, name, and sample count — use the returned lineage as the biome_lineage filter in ebi-metagenomics.study_search. Data: EMBL-EBI MGnify (www.ebi.ac.uk/metagenomics), no auth required. It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
ebi-metagenomics.biomes.browse accepts 3 parameters: page, lineage, page_size. 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 ebi-metagenomics.biomes.browse: 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.
ebi-metagenomics.biomes.browse 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 ebi-metagenomics.biomes.browse 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 ebi-metagenomics.biomes.browse. 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.
ebi-metagenomics.biomes.browse 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