fda_drug_lookup
Look up FDA drug label info by NDC code, brand name, or generic name. Returns indications, dosage, warnings, contraindications, mechanism, manufacturer, and DEA scheduling. Used for clinical decision support, pharmacy automation, drug-info chatbots.
This record as markdown: /tools/io-github-blackboxfoundry-livedatalink/fda-drug-lookup.md
What fda_drug_lookup does on Livedatalink
AI agents call fda_drug_lookup to retrieve information from Livedatalink 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 |
|---|---|---|---|
limit | number | — | Maximum rows to return (default 25, max 100). |
query | string | Yes | NDC code (e.g. '0002-1407'), brand name (e.g. 'Lipitor'), or generic name (e.g. 'atorvastatin'). |
Parameters from the server's own tool schema.
Why fda_drug_lookup is rated Low
This is a straightforward data retrieval tool that queries FDA drug information and returns reference data. It has no side effects, does not modify data, and does not trigger external operations. While the data returned could inform clinical decisions, the tool itself only reads and presents publicly available FDA label information.
From the tool's definition Tool performs lookup and retrieval operations: 'Look up FDA drug label info', 'Returns indications, dosage, warnings, contraindications, mechanism, manufacturer, and DEA scheduling.' No modification, deletion, or execution of external systems described.
Attacks that exploit this kind of access
The rule that runs fda_drug_lookup safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Livedatalink, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For fda_drug_lookup, this is the rule to start with:
fda_drug_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 Livedatalink, apply this rule, and every fda_drug_lookup call is checked against it from then on.
Questions about fda_drug_lookup
Look up FDA drug label info by NDC code, brand name, or generic name. Returns indications, dosage, warnings, contraindications, mechanism, manufacturer, and DEA scheduling. Used for clinical decision support, pharmacy automation, drug-info chatbots. It is categorised as a Read tool in the Livedatalink MCP Server, which means it retrieves data without modifying state.
fda_drug_lookup accepts 2 parameters: limit, query. Required: query. The full parameter table on this page comes from the server's own tool schema.
Register the Livedatalink MCP server in PolicyLayer and add a rule for fda_drug_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 Livedatalink. Nothing to install.
fda_drug_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 fda_drug_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 fda_drug_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.
fda_drug_lookup is provided by the Livedatalink MCP server (https://livedatalink.ai/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Livedatalink, and thousands of servers like it.
This server
Across the catalogue