Retrieve FDA FAERS post-market adverse event reports and safety signals for a drug or active ingredient. Input: drug brand name or generic active ingredient (e.g. 'ibuprofen', 'metformin'). Returns: total FAERS report counts, serious outcome counts, death report counts, top 10 adverse reactions b...
Risk signalsAccepts freeform code/query input (query)
Part of the Pharma Regulatory server.
Free to start. No card required.
AI agents call check_adverse_events 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 check_adverse_events 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": {
"check_adverse_events": {}
}
}See the full Pharma Regulatory policy for all 4 tools.
These attack patterns abuse exactly the kind of access check_adverse_events 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.
Retrieve FDA FAERS post-market adverse event reports and safety signals for a drug or active ingredient. Input: drug brand name or generic active ingredient (e.g. 'ibuprofen', 'metformin'). Returns: total FAERS report counts, serious outcome counts, death report counts, top 10 adverse reactions by frequency, most common patient age groups, and drug ranking. Source: FDA Adverse Event Reporting System (FAERS) — 2,000 top-reported drugs with aggregated safety signals. For pharmacovigilance and post-market drug safety assessment. Do not use for interaction mechanisms (use check_drug_interactions), regulatory approvals (use check_drug), or supplement/nutrition questions.. 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 check_adverse_events: 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.
check_adverse_events 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 check_adverse_events 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 check_adverse_events. 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.
check_adverse_events 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.