rxnorm.drugs.search
Search the NIH RxNorm drug database by generic name, brand name, or ingredient. Returns standardized drug concepts with their RxCUI identifiers, term types (ingredient, brand name, clinical drug, branded drug), and synonyms. RxNorm is the US standard drug nomenclature used by EHRs, pharmacies, an...
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/rxnorm.drugs.search.md
What rxnorm.drugs.search does on Apibase
AI agents call rxnorm.drugs.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 |
|---|---|---|---|
tty | string | — | Filter by RxNorm term type (TTY). Common values: IN=Ingredient, BN=Brand Name, SCD=Semantic Clinical Drug (includes dose/form), SBD=Semantic Branded Drug. Omit |
name | string | Yes | Drug name to search — generic name (e.g. "aspirin"), brand name (e.g. "Tylenol"), or ingredient (e.g. "acetaminophen") |
limit | integer | — | Maximum number of drug concepts to return (1–100, default 20) |
Parameters from the server's own tool schema.
Why rxnorm.drugs.search is rated Low
Tool queries a public medical database and retrieves drug information without creating, modifying, or deleting data.
From the tool's definition Search NIH RxNorm drug database, returns standardized drug concepts, no modifications.
Attacks that exploit this kind of access
The rule that runs rxnorm.drugs.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 rxnorm.drugs.search, this is the rule to start with:
rxnorm.drugs.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 rxnorm.drugs.search call is checked against it from then on.
Questions about rxnorm.drugs.search
Search the NIH RxNorm drug database by generic name, brand name, or ingredient. Returns standardized drug concepts with their RxCUI identifiers, term types (ingredient, brand name, clinical drug, branded drug), and synonyms. RxNorm is the US standard drug nomenclature used by EHRs, pharmacies, and insurers. Use the RxCUI from results with rxnorm.drugs.properties and rxnorm.drugs.class for deeper drug information. Filter by term type (tty) to focus on ingredients (IN), brand names (BN), or clinical drug formulations (SCD/SBD). It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
rxnorm.drugs.search accepts 3 parameters: tty, name, limit. Required: name. 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 rxnorm.drugs.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.
rxnorm.drugs.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 rxnorm.drugs.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 rxnorm.drugs.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.
rxnorm.drugs.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