biomodels.model.detail
Get full metadata for a specific BioModels mathematical model by accession ID (e.g. "BIOMD0000000001" for the Edelstein 1996 nicotinic acetylcholine receptor model). Returns model name, curation status, modelling approach (ODE, logical, stochastic), SBML format and version, description of the bio...
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/biomodels.model.detail.md
What biomodels.model.detail does on Apibase
AI agents call biomodels.model.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 |
|---|---|---|---|
model_id | string | Yes | BioModels accession identifier. Curated models use BIOMD prefix followed by 10 digits (e.g. "BIOMD0000000001", "BIOMD0000000295"). Author-submitted models use M |
Parameters from the server's own tool schema.
Why biomodels.model.detail is rated Low
Retrieves read-only model metadata and annotations from BioModels database with no side effects.
From the tool's definition Get full metadata for a specific BioModels mathematical model by accession ID. Returns model name, curation status, modelling approach
Attacks that exploit this kind of access
The rule that runs biomodels.model.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 biomodels.model.detail, this is the rule to start with:
biomodels.model.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 biomodels.model.detail call is checked against it from then on.
Questions about biomodels.model.detail
Get full metadata for a specific BioModels mathematical model by accession ID (e.g. "BIOMD0000000001" for the Edelstein 1996 nicotinic acetylcholine receptor model). Returns model name, curation status, modelling approach (ODE, logical, stochastic), SBML format and version, description of the biological system, linked peer-reviewed publication (PubMed ID, journal, year, authors), contributor roles (curator, submitter, encoder), and model-level ontology annotations (GO terms, disease terms, taxonomy, pathway cross-references). Use biomodels.model.search first to discover accession IDs. CC0 Public Domain — EMBL-EBI BioModels Database. It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
biomodels.model.detail accepts 1 parameter: model_id. Required: model_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 biomodels.model.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.
biomodels.model.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 biomodels.model.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 biomodels.model.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.
biomodels.model.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