AI agents call get-drug-by-generic-name to retrieve information from OpenFDA without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Even though get-drug-by-generic-name 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
Get drug information by generic (active ingredient) name. Useful when you know the generic name but not the brand name. Returns all brand versions of the generic drug. It is categorised as a Read tool in the OpenFDA MCP Server, which means it retrieves data without modifying state.
Register the OpenFDA MCP server in PolicyLayer and add a rule for get-drug-by-generic-name: 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.
get-drug-by-generic-name 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-by-generic-name 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-by-generic-name. 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-by-generic-name is provided by the OpenFDA MCP server (ythalorossy/openfda). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.