Get NDC codes for a specific drug by its SET ID
AI agents call get_drug_ndcs to retrieve information from DailyMed MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves pharmaceutical reference data (NDC codes) from a read-only FDA database without creating, modifying, deleting, executing code, or involving financial transactions. It is a simple lookup query with no side effects. The lowest severity applies since the data is public FDA information and misuse (e.g., retrieving NDC codes for many drugs) poses minimal harm.
From the tool's definition Tool name 'get_drug_ndcs' and description 'Get NDC codes for a specific drug by its SET ID' indicate a retrieval operation that queries the DailyMed database for National Drug Code identifiers associated with a drug.
Attacks that exploit this kind of access
Get NDC codes for a specific drug by its SET ID. It is categorised as a Read tool in the DailyMed MCP Server MCP Server, which means it retrieves data without modifying state.
Register the DailyMed MCP Server MCP server in PolicyLayer and add a rule for get_drug_ndcs: 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 DailyMed MCP Server. Nothing to install.
get_drug_ndcs 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 get_drug_ndcs 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 get_drug_ndcs. 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.
get_drug_ndcs is provided by the DailyMed MCP Server MCP server (rowanerasmus/dailymed-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →