Search for UNII codes using various parameters with pagination support
AI agents call search_uniis 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 FDA reference data (UNII codes) without creating, modifying, executing external operations, deleting data, or involving financial transactions. It falls squarely into the Read category as a data lookup function. The pagination support further confirms it is a standard query endpoint.
From the tool's definition Tool name 'search_uniis' combined with description 'Search for UNII codes using various parameters' indicates a query/retrieval operation. UNII (Unique Ingredient Identifier) codes are static reference identifiers in FDA databases.
Attacks that exploit this kind of access
Search for UNII codes using various parameters 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 search_uniis: 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_uniis 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_uniis 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_uniis. 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_uniis 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 →