icd11.disease.lookup
Retrieve the title and classification type for a specific ICD-11 code. Returns the human-readable disease/condition name and whether the code is a primary stem code or an extension modifier. Use to validate ICD-11 codes, decode alphanumeric codes in clinical records, or verify correct code usage....
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/icd11.disease.lookup.md
What icd11.disease.lookup does on Apibase
AI agents call icd11.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 |
|---|---|---|---|
code | string | Yes | ICD-11 code to look up — alphanumeric code from the ICD-11 classification (e.g. "BA00" for essential hypertension, "5A10" for type 1 diabetes, "CA40" for pneumo |
Parameters from the server's own tool schema.
Why icd11.disease.lookup is rated Low
Tool queries public ICD-11 disease classification data without modifying, deleting, or executing external operations.
From the tool's definition Retrieve title and classification type for ICD-11 code. Returns human-readable disease name. No side effects.
Risk signalsAccepts freeform code/query input (code)
Attacks that exploit this kind of access
The rule that runs icd11.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 icd11.disease.lookup, this is the rule to start with:
icd11.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 icd11.disease.lookup call is checked against it from then on.
Questions about icd11.disease.lookup
Retrieve the title and classification type for a specific ICD-11 code. Returns the human-readable disease/condition name and whether the code is a primary stem code or an extension modifier. Use to validate ICD-11 codes, decode alphanumeric codes in clinical records, or verify correct code usage. Examples: BA00 → Essential hypertension, 5A10 → Type 1 diabetes mellitus, CA40 → Pneumonia. No auth — US National Library of Medicine public domain, unlimited free. It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
icd11.disease.lookup accepts 1 parameter: code. Required: code. 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 icd11.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.
icd11.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 icd11.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 icd11.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.
icd11.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