Low Risk

openfda_lookup_ndc

Look up drugs in the NDC (National Drug Code) Directory. Identify drug products by NDC code, find active ingredients, packaging details, or manufacturer info. Pair with openfda_get_drug_label using the returned brand_name or set_id to read the package insert.

Part of the Openfda server.

openfda_lookup_ndc is read-only, but an agent in a loop can still rack up calls and cost. PolicyLayer caps every call before it runs. Live in minutes.

SECURE OPENFDA →

Free to start. No card required.

AI agents call openfda_lookup_ndc to retrieve information from Openfda without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.

Even though openfda_lookup_ndc only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.

Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "openfda_lookup_ndc": {}
  }
}

See the full Openfda policy for all 12 tools.

Get this rule live on your own Openfda server in minutes. PolicyLayer enforces it on every call, before it runs.

ENFORCE ON MY OPENFDA →

View all 12 tools →

These attack patterns abuse exactly the kind of access openfda_lookup_ndc gives an agent. Each links to the full case and the policy that stops it:

Browse the full MCP Attack Database →

Every attack above starts with a tool call. PolicyLayer checks each one against your policy first, so openfda_lookup_ndc only ever does what you allow.

SECURE OPENFDA →

Other read tools across the catalogue. The same approach applies to each: allow, with a rate cap to control cost.

What does the openfda_lookup_ndc tool do? +

Look up drugs in the NDC (National Drug Code) Directory. Identify drug products by NDC code, find active ingredients, packaging details, or manufacturer info. Pair with openfda_get_drug_label using the returned brand_name or set_id to read the package insert.. It is categorised as a Read tool in the Openfda MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on openfda_lookup_ndc? +

Register the Openfda MCP server in PolicyLayer and add a rule for openfda_lookup_ndc: 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 Openfda. Nothing to install.

What risk level is openfda_lookup_ndc? +

openfda_lookup_ndc is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit openfda_lookup_ndc? +

Yes. Add a rate_limit block to the openfda_lookup_ndc 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.

How do I block openfda_lookup_ndc completely? +

Set action: deny in the PolicyLayer policy for openfda_lookup_ndc. 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.

What MCP server provides openfda_lookup_ndc? +

openfda_lookup_ndc is provided by the Openfda MCP server (https://openfda.caseyjhand.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Openfda tool call.

Deterministic rules across all 12 Openfda tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

4,600+ MCP servers and 31,000+ tools scanned and risk-classified.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.