icd11.disease.primary_search
Search ICD-11 codes returning only primary (stem) diagnosis codes — filters out extension/modifier codes. Stem codes represent principal diagnoses and standalone conditions, while extension codes are qualifiers (severity, laterality, histopathology). Use this when you need clean primary diagnoses...
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/icd11.disease.primary-search.md
What icd11.disease.primary_search does on Apibase
AI agents call icd11.disease.primary_search 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 | Clinical search term to find primary (stem) ICD-11 diagnosis codes only — excludes extension/modifier codes (e.g. "cancer", "fever", "infection") |
max_results | integer | — | Maximum number of primary (stem) codes to return (1-25). Default: 10 |
Parameters from the server's own tool schema.
Why icd11.disease.primary_search is rated Low
Tool queries disease classification data without modifying, executing external operations, or accessing sensitive information.
From the tool's definition Search ICD-11 codes returning primary diagnosis codes; no auth, public domain
Attacks that exploit this kind of access
The rule that runs icd11.disease.primary_search 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.primary_search, this is the rule to start with:
icd11.disease.primary_search 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.primary_search call is checked against it from then on.
Questions about icd11.disease.primary_search
Search ICD-11 codes returning only primary (stem) diagnosis codes — filters out extension/modifier codes. Stem codes represent principal diagnoses and standalone conditions, while extension codes are qualifiers (severity, laterality, histopathology). Use this when you need clean primary diagnoses for: mortality coding, disease surveillance, DRG assignment, or primary diagnosis classification. 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.primary_search 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.primary_search: 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.primary_search 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.primary_search 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.primary_search. 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.primary_search 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