One-call drug situational awareness: whether a drug is currently in FDA shortage, any open/recent FDA recalls, and FDA NDC-directory metadata (labeler, DEA schedule, pharm class). Give a drug name (resolved via RxNorm), or an exact rxcui or ndc. Returns hasCurrentShortage/hasOpenRecall plus per-s...
AI agents call medical.drug-status to retrieve information from Mcp without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs informational lookups against public FDA and NIH databases. It queries and returns existing data about drug shortages, recalls, and regulatory metadata without side effects. The tool is read-only—it cannot create, modify, delete, or execute operations, nor does it involve financial transactions.
From the tool's definition Tool retrieves drug status information: 'whether a drug is currently in FDA shortage, any open/recent FDA recalls, and FDA NDC-directory metadata'. Returns data blocks with 'hasCurrentShortage/hasOpenRecall' status. Uses 'Free, public-domain FDA + NIH data'.
Attacks that exploit this kind of access
One-call drug situational awareness: whether a drug is currently in FDA shortage, any open/recent FDA recalls, and FDA NDC-directory metadata (labeler, DEA schedule, pharm class). Give a drug name (resolved via RxNorm), or an exact rxcui or ndc. Returns hasCurrentShortage/hasOpenRecall plus per-source found/error blocks. Free, public-domain FDA + NIH data. It is categorised as a Read tool in the Mcp MCP Server, which means it retrieves data without modifying state.
Register the MCP server in PolicyLayer and add a rule for medical.drug-status: 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 Mcp. Nothing to install.
medical.drug-status 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 medical.drug-status 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 medical.drug-status. 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.
medical.drug-status is provided by the MCP server (@2sio/mcp). 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 →