ebi-metagenomics.studies.search

SERVERApibase SOURCEapibase-mcp-client

Medium RISK CLASS

Category Write

Parameters 40 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-whiteknightonhorse-apibase/ebi-metagenomics.studies.search.md

WHAT IT DOES

What ebi-metagenomics.studies.search does on Apibase

AI agents use ebi-metagenomics.studies.search to create or update resources in Apibase, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Apibase environment.

Parameter	Type	Required	Description
`page`	integer	—	Page number, 1-indexed (default 1).
`query`	string	—	Free-text search across study name, abstract, and bioproject, e.g. "gut microbiome".
`page_size`	integer	—	Number of studies to return per page, 1-25 (default 10).
`biome_lineage`	string	—	Filter to studies classified under this biome lineage, e.g. "root:Host-associated:Human" or "root:Environmental:Aquatic:Marine". Get valid lineages from ebi-met

Parameters from the server's own tool schema.

RISK

Why ebi-metagenomics.studies.search is rated Medium

An AI agent can call ebi-metagenomics.studies.search faster than any human can review: one bad instruction and it creates or modifies resources in Apibase by the hundred, each call as confident as the last.

Risk signalsAdmin/system-level operation

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs ebi-metagenomics.studies.search 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.search, this is the rule to start with:

ebi-metagenomics.studies.search Rate-limited

ebi-metagenomics.studies.search stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "ebi-metagenomics.studies.search": {
      "limits": [
        {
          "counter": "ebi-metagenomics.studies.search_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Apibase, apply this rule, and every ebi-metagenomics.studies.search call is checked against it from then on.

FAQ

Questions about ebi-metagenomics.studies.search

What does the ebi-metagenomics.studies.search tool do? +

Search EBI's MGnify metagenomics archive for studies by free-text query (name/abstract/bioproject) and/or biome lineage (e.g. "root:Host-associated:Human"). Returns each study's accession, name, abstract, bioproject, sequencing centre, sample count, last-update date, and associated biome lineages. Data: EMBL-EBI MGnify (www.ebi.ac.uk/metagenomics), no auth required. It is categorised as a Write tool in the Apibase MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

What parameters does ebi-metagenomics.studies.search accept? +

ebi-metagenomics.studies.search accepts 4 parameters: page, query, page_size, biome_lineage. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on ebi-metagenomics.studies.search? +

Register the Apibase MCP server in PolicyLayer and add a rule for ebi-metagenomics.studies.search: 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.

What risk level is ebi-metagenomics.studies.search? +

ebi-metagenomics.studies.search is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit ebi-metagenomics.studies.search? +

Yes. Add a rate_limit block to the ebi-metagenomics.studies.search 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.

How do I block ebi-metagenomics.studies.search completely? +

Set action: deny in the PolicyLayer policy for ebi-metagenomics.studies.search. 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.

What MCP server provides ebi-metagenomics.studies.search? +

ebi-metagenomics.studies.search 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.

KEEP EXPLORING

More on Apibase, and thousands of servers like it.

This server

All 1384 Apibase tools →

Across the catalogue

The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →