Get all available drug names in the DailyMed database with pagination support
AI agents call get_all_drug_names 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 and lists drug names from a read-only FDA database. It has no side effects, does not execute code or commands, does not modify data, and does not involve financial transactions. The pagination support confirms it is a query/listing operation. The blast radius of misuse is minimal—an agent could only enumerate drug names from publicly available FDA data.
From the tool's definition Tool name 'get_all_drug_names' and description 'Get all available drug names in the DailyMed database with pagination support' indicate a data retrieval operation with no modification or execution capabilities.
Attacks that exploit this kind of access
Get all available drug names in the DailyMed database with pagination support. 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_all_drug_names: 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_all_drug_names 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_all_drug_names 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_all_drug_names. 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_all_drug_names 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 →