orphadata.raredisease.disease_phenotypes
Get clinical signs and symptoms (HPO phenotypes) for a rare disease by its Orphanet ORPHAcode. Returns HPO identifiers and terms annotated with frequency categories (Very frequent 99-80%, Frequent 79-30%, Occasional 29-5%) and whether each sign is a diagnostic criterion. Up to 68+ HPO terms per d...
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/orphadata.raredisease.disease-phenotypes.md
What orphadata.raredisease.disease_phenotypes does on Apibase
AI agents call orphadata.raredisease.disease_phenotypes 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. |
orphacode | integer | Yes | Orphanet ORPHAcode of the rare disease whose HPO phenotypes to retrieve (e.g. 558 for Marfan syndrome). |
Parameters from the server's own tool schema.
Why orphadata.raredisease.disease_phenotypes is rated Low
Tool retrieves medical reference data about rare disease phenotypes without modifying or executing anything.
From the tool's definition Get clinical signs and symptoms for a rare disease by its Orphanet ORPHAcode.
Attacks that exploit this kind of access
The rule that runs orphadata.raredisease.disease_phenotypes 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_phenotypes, this is the rule to start with:
orphadata.raredisease.disease_phenotypes 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_phenotypes call is checked against it from then on.
Questions about orphadata.raredisease.disease_phenotypes
Get clinical signs and symptoms (HPO phenotypes) for a rare disease by its Orphanet ORPHAcode. Returns HPO identifiers and terms annotated with frequency categories (Very frequent 99-80%, Frequent 79-30%, Occasional 29-5%) and whether each sign is a diagnostic criterion. Up to 68+ HPO terms per disease, cited from PubMed. 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_phenotypes accepts 2 parameters: lang, orphacode. Required: orphacode. 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_phenotypes: 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_phenotypes 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_phenotypes 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_phenotypes. 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_phenotypes 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