Search for RxNorm mappings by drug name
AI agents call search_by_rxnorm_mapping 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 RxNorm mapping information based on drug name queries. It performs a lookup/search operation against the DailyMed database, which is a read-only informational database of FDA drug information. There is no capability to modify, delete, or execute code. The worst case misuse would be information disclosure of already-public FDA data, resulting in minimal blast radius.
From the tool's definition Tool description states 'Search for RxNorm mappings by drug name' - a query operation that retrieves data from the FDA DailyMed database.
Attacks that exploit this kind of access
Search for RxNorm mappings by drug name. 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 search_by_rxnorm_mapping: 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.
search_by_rxnorm_mapping 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 search_by_rxnorm_mapping 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 search_by_rxnorm_mapping. 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.
search_by_rxnorm_mapping 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 →