Get version history for a specific drug by its SET ID
AI agents call get_drug_history 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 version history information from the FDA DailyMed database—a read-only operation with no side effects. It does not create, modify, delete, or execute any code. The action is purely informational, querying existing data about a drug's historical versions.
From the tool's definition Tool name 'get_drug_history' and description 'Get version history for a specific drug by its SET ID' indicate a retrieval operation that queries historical metadata without modifying or deleting data.
Attacks that exploit this kind of access
Get version history 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_history: 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_history 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_history 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_history. 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_history 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 →