icd11.disease.autocomplete
Get fast ICD-11 code autocomplete suggestions for a partial clinical term. Returns up to 10 matching codes and titles as the user types — ideal for building clinical coding interfaces, EHR integrations, or any application requiring responsive disease/diagnosis search. Input partial terms like "di...
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/icd11.disease.autocomplete.md
What icd11.disease.autocomplete does on Apibase
AI agents call icd11.disease.autocomplete 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 |
|---|---|---|---|
terms | string | Yes | Partial clinical term for autocomplete suggestions (e.g. "dia" → diabetes options, "hyp" → hypertension options) |
max_results | integer | — | Maximum number of autocomplete suggestions (1-10). Default: 5 |
Parameters from the server's own tool schema.
Why icd11.disease.autocomplete is rated Low
Retrieves ICD-11 code suggestions without modifying data or triggering side effects.
From the tool's definition autocomplete suggestions for partial clinical term, returns matching codes
Attacks that exploit this kind of access
The rule that runs icd11.disease.autocomplete 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.autocomplete, this is the rule to start with:
icd11.disease.autocomplete 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.autocomplete call is checked against it from then on.
Questions about icd11.disease.autocomplete
Get fast ICD-11 code autocomplete suggestions for a partial clinical term. Returns up to 10 matching codes and titles as the user types — ideal for building clinical coding interfaces, EHR integrations, or any application requiring responsive disease/diagnosis search. Input partial terms like "dia" → diabetes options, "hyp" → hypertension, "pneu" → 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.autocomplete accepts 2 parameters: terms, max_results. Required: terms. 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.autocomplete: 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.autocomplete 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.autocomplete 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.autocomplete. 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.autocomplete 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