medlineplus.clinical.icd10_lookup
Look up patient-friendly health information for an ICD-10-CM diagnosis code via the NLM MedlinePlus Connect service. Returns MedlinePlus topic titles, URLs, and plain-language summaries for conditions matching the code (e.g. E11 → Type 2 Diabetes, J18.9 → Pneumonia, I21 → Myocardial Infarction). ...
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/medlineplus.clinical.icd10-lookup.md
What medlineplus.clinical.icd10_lookup does on Apibase
AI agents call medlineplus.clinical.icd10_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-10-CM diagnosis code to look up (e.g. E11 for Type 2 Diabetes, J18.9 for Pneumonia). |
language | string | — | Response language: en (English) or es (Spanish). Default: en. |
Parameters from the server's own tool schema.
Why medlineplus.clinical.icd10_lookup is rated Low
Tool queries public medical reference data without modifying, executing code, or accessing sensitive patient records.
From the tool's definition Look up patient-friendly health information, returns MedlinePlus topic titles, URLs, summaries
Risk signalsAccepts freeform code/query input (code)
Attacks that exploit this kind of access
The rule that runs medlineplus.clinical.icd10_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 medlineplus.clinical.icd10_lookup, this is the rule to start with:
medlineplus.clinical.icd10_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 medlineplus.clinical.icd10_lookup call is checked against it from then on.
Questions about medlineplus.clinical.icd10_lookup
Look up patient-friendly health information for an ICD-10-CM diagnosis code via the NLM MedlinePlus Connect service. Returns MedlinePlus topic titles, URLs, and plain-language summaries for conditions matching the code (e.g. E11 → Type 2 Diabetes, J18.9 → Pneumonia, I21 → Myocardial Infarction). Supports English and Spanish responses (language=es). Used in EHR/clinical contexts to link clinical codes to patient education materials. Source: US NLM MedlinePlus Connect — public domain, no auth, unlimited free. It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
medlineplus.clinical.icd10_lookup accepts 2 parameters: code, language. 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 medlineplus.clinical.icd10_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.
medlineplus.clinical.icd10_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 medlineplus.clinical.icd10_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 medlineplus.clinical.icd10_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.
medlineplus.clinical.icd10_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