rxnorm.drugs.ndc_lookup
Look up a drug product by its National Drug Code (NDC) to retrieve its RxNorm mapping and active status. The NDC is the 10- or 11-digit code printed on every US drug package. Returns the standardized 11-digit NDC, current active/inactive status in RxNorm, the mapped RxCUI, the concept name, and t...
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/rxnorm.drugs.ndc-lookup.md
What rxnorm.drugs.ndc_lookup does on Apibase
AI agents call rxnorm.drugs.ndc_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 |
|---|---|---|---|
ndc | string | Yes | National Drug Code (NDC) in any of the standard formats: 10-digit (0069-3060-86), 11-digit (00069306086), or hyphenated (0069-3060-86). Found on drug packaging |
Parameters from the server's own tool schema.
Why rxnorm.drugs.ndc_lookup is rated Low
Tool queries drug database for informational lookup with no side effects or modifications.
From the tool's definition Look up drug product, retrieve RxNorm mapping, returns standardized code and status
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs rxnorm.drugs.ndc_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 rxnorm.drugs.ndc_lookup, this is the rule to start with:
rxnorm.drugs.ndc_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 rxnorm.drugs.ndc_lookup call is checked against it from then on.
Questions about rxnorm.drugs.ndc_lookup
Look up a drug product by its National Drug Code (NDC) to retrieve its RxNorm mapping and active status. The NDC is the 10- or 11-digit code printed on every US drug package. Returns the standardized 11-digit NDC, current active/inactive status in RxNorm, the mapped RxCUI, the concept name, and the data sources that include this NDC. Useful for medication verification, formulary checks, and cross-referencing between pharmacy systems and RxNorm. It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
rxnorm.drugs.ndc_lookup accepts 1 parameter: ndc. Required: ndc. 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.ndc_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.
rxnorm.drugs.ndc_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 rxnorm.drugs.ndc_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 rxnorm.drugs.ndc_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.
rxnorm.drugs.ndc_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