ebi-metagenomics.samples.list
List the biological samples belonging to a MGnify study (study_accession from ebi-metagenomics.study_search or ebi-metagenomics.study_detail). Returns each sample's accession, name, description, BioSample ID, latitude/longitude, geographic location, collection date, environment biome/feature/mate...
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/ebi-metagenomics.samples.list.md
What ebi-metagenomics.samples.list does on Apibase
AI agents call ebi-metagenomics.samples.list 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). |
page_size | integer | — | Number of samples to return per page, 1-50 (default 10). |
study_accession | string | Yes | MGnify study accession, e.g. "MGYS00006862", from ebi-metagenomics.study_search. |
Parameters from the server's own tool schema.
Why ebi-metagenomics.samples.list is rated Low
Retrieves and queries public biological sample metadata from EMBL-EBI MGnify without authentication or side effects.
From the tool's definition List the biological samples belonging to a MGnify study. Returns each sample's accession, name, description, metadata.
Attacks that exploit this kind of access
The rule that runs ebi-metagenomics.samples.list 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.samples.list, this is the rule to start with:
ebi-metagenomics.samples.list 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.samples.list call is checked against it from then on.
Questions about ebi-metagenomics.samples.list
List the biological samples belonging to a MGnify study (study_accession from ebi-metagenomics.study_search or ebi-metagenomics.study_detail). Returns each sample's accession, name, description, BioSample ID, latitude/longitude, geographic location, collection date, environment biome/feature/material, host taxon ID, species, and metadata key/value pairs. 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.samples.list accepts 3 parameters: page, page_size, study_accession. Required: study_accession. 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.samples.list: 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.samples.list 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.samples.list 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.samples.list. 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.samples.list 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