Search across all pharmaceutical regulatory and safety datasets by disease area, drug class, safety endpoint, indication, target, or regulatory keyword. Input: keyword for broad discovery (e.g. 'diabetes', 'antibiotic', 'hepatotoxicity', 'pregnancy', 'cancer'). Returns: cross-dataset matches from...
Risk signalsAccepts freeform code/query input (query)
Part of the Pharma Regulatory server.
Free to start. No card required.
AI agents call search_pharma to retrieve information from Pharma Regulatory without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.
Even though search_pharma only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.
Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.
{
"version": "1",
"default": "deny",
"tools": {
"search_pharma": {}
}
}See the full Pharma Regulatory policy for all 4 tools.
These attack patterns abuse exactly the kind of access search_pharma gives an agent. Each links to the full case and the policy that stops it:
Other read tools across the catalogue. The same approach applies to each: allow, with a rate cap to control cost.
Search across all pharmaceutical regulatory and safety datasets by disease area, drug class, safety endpoint, indication, target, or regulatory keyword. Input: keyword for broad discovery (e.g. 'diabetes', 'antibiotic', 'hepatotoxicity', 'pregnancy', 'cancer'). Returns: cross-dataset matches from DrugBank, WHO Essential Medicines, Australian TGA ARTG, FDA FAERS, drug interactions, FDA NDI, and ChEMBL bioactivity — each with dataset labels, identifiers, and source-specific fields. Database: 7 pharmaceutical datasets totaling 45,000+ records. For pharmaceutical research and regulatory intelligence discovery. Do not use when the exact drug name is known (use check_drug, check_drug_interactions, or check_adverse_events for targeted lookups).. It is categorised as a Read tool in the Pharma Regulatory MCP Server, which means it retrieves data without modifying state.
Register the Pharma Regulatory MCP server in PolicyLayer and add a rule for search_pharma: 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 Pharma Regulatory. Nothing to install.
search_pharma 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_pharma 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_pharma. 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_pharma is provided by the Pharma Regulatory MCP server (https://pharma-mcp-server.rootsbybenda.workers.dev/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 4 Pharma Regulatory tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
4,600+ MCP servers and 31,000+ tools scanned and risk-classified.