orphadata.raredisease.disease_lookup
Search Orphanet rare disease database by disease name and retrieve cross-references to major medical coding systems. Returns ORPHAcode, full disease definition, synonyms, and validated cross-references to ICD-10, ICD-11, OMIM, MONDO, MeSH, MedDRA, UMLS, and Orphanet URL. Covers 4,245+ rare diseas...
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/orphadata.raredisease.disease-lookup.md
What orphadata.raredisease.disease_lookup does on Apibase
AI agents call orphadata.raredisease.disease_lookup 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 |
|---|---|---|---|
lang | string | — | Response language (default: en). Supported: en, fr, de, es, it, pt, nl, pl, cs, tr, uk, zh. |
name | string | Yes | Preferred name (or part of it) of the rare disease to search (e.g. "Marfan syndrome", "cystic fibrosis"). |
Parameters from the server's own tool schema.
Why orphadata.raredisease.disease_lookup is rated Low
Tool queries medical database and returns structured data without modifications or side effects.
From the tool's definition Search database, retrieve cross-references, returns disease definitions and codes.
Attacks that exploit this kind of access
The rule that runs orphadata.raredisease.disease_lookup 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 orphadata.raredisease.disease_lookup, this is the rule to start with:
orphadata.raredisease.disease_lookup 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 orphadata.raredisease.disease_lookup call is checked against it from then on.
Questions about orphadata.raredisease.disease_lookup
Search Orphanet rare disease database by disease name and retrieve cross-references to major medical coding systems. Returns ORPHAcode, full disease definition, synonyms, and validated cross-references to ICD-10, ICD-11, OMIM, MONDO, MeSH, MedDRA, UMLS, and Orphanet URL. Covers 4,245+ rare diseases. Supports 12 languages (en, fr, de, es, it, pt, nl, pl, cs, tr, uk, zh). Source: Orphadata / Orphanet — CC BY 4.0, no auth, unlimited free. It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
orphadata.raredisease.disease_lookup accepts 2 parameters: lang, name. Required: name. 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 orphadata.raredisease.disease_lookup: 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.
orphadata.raredisease.disease_lookup 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 orphadata.raredisease.disease_lookup 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 orphadata.raredisease.disease_lookup. 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.
orphadata.raredisease.disease_lookup 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