ebi-metagenomics.studies.detail
Get full detail for one MGnify study by its accession (e.g. "MGYS00006862") from ebi-metagenomics.study_search: study name, abstract, bioproject, secondary accession, sequencing centre, sample count, privacy/release status, data origination, and biome lineages. Data: EMBL-EBI MGnify (www.ebi.ac.u...
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/ebi-metagenomics.studies.detail.md
What ebi-metagenomics.studies.detail does on Apibase
AI agents call ebi-metagenomics.studies.detail 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 |
|---|---|---|---|
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.studies.detail is rated Low
Retrieves study metadata from public database with no side effects or authentication requirements.
From the tool's definition Get full detail for one MGnify study by its accession
Attacks that exploit this kind of access
The rule that runs ebi-metagenomics.studies.detail 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.studies.detail, this is the rule to start with:
ebi-metagenomics.studies.detail 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.studies.detail call is checked against it from then on.
Questions about ebi-metagenomics.studies.detail
Get full detail for one MGnify study by its accession (e.g. "MGYS00006862") from ebi-metagenomics.study_search: study name, abstract, bioproject, secondary accession, sequencing centre, sample count, privacy/release status, data origination, and biome lineages. 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.studies.detail accepts 1 parameter: accession. Required: 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.studies.detail: 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.studies.detail 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.studies.detail 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.studies.detail. 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.studies.detail 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