openfda_drug
FDA drug facts by brand/generic name or NDC from openFDA: label sections (boxed warning, indications, dosage, contraindications, warnings, adverse reactions, interactions, or any SPL field), FAERS adverse-event report totals with serious count and top reported reactions, and the latest enforcemen...
This record as markdown: /tools/com-it-scorptech-x402/openfda-drug.md
What openfda_drug does on ScorpTech x402 API
AI agents call openfda_drug to retrieve information from ScorpTech x402 API 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 | — | Alternative: product NDC (0573-0164) or package NDC (0573-0164-30) |
name | string | — | Brand or generic drug name (alias: drug) |
limit | integer | — | Top adverse reactions to return, 1-25 (default 10) |
include | string | — | Comma list of label, events, recalls (default all) |
maxChars | integer | — | Max characters per label section, 100-10000 (default 1200) |
sections | string | — | Comma list of openFDA label fields, or "all" (default: key safety sections) |
Parameters from the server's own tool schema.
Why openfda_drug is rated Low
Even though openfda_drug only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Attacks that exploit this kind of access
The rule that runs openfda_drug safely
PolicyLayer is an MCP gateway: it sits between your AI agents and ScorpTech x402 API, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For openfda_drug, this is the rule to start with:
openfda_drug 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 ScorpTech x402 API, apply this rule, and every openfda_drug call is checked against it from then on.
Questions about openfda_drug
FDA drug facts by brand/generic name or NDC from openFDA: label sections (boxed warning, indications, dosage, contraindications, warnings, adverse reactions, interactions, or any SPL field), FAERS adverse-event report totals with serious count and top reported reactions, and the latest enforcement recalls with class and reason. Not for clinical use; the response carries FDA's disclaimer. Price: $0.01 USDC per successful call (x402, Solana). Same tool over HTTPS: GET https://scorptech.it.com/api/x402/v1/openfda-drug. It is categorised as a Read tool in the ScorpTech x402 API MCP Server, which means it retrieves data without modifying state.
openfda_drug accepts 6 parameters: ndc, name, limit, include, maxChars, sections. The full parameter table on this page comes from the server's own tool schema.
Register the ScorpTech x402 API MCP server in PolicyLayer and add a rule for openfda_drug: 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 ScorpTech x402 API. Nothing to install.
openfda_drug 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 openfda_drug 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 openfda_drug. 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.
openfda_drug is provided by the ScorpTech x402 API MCP server (https://scorptech.it.com/api/x402/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on ScorpTech x402 API, and thousands of servers like it.
This server
Across the catalogue