fda_drug_adverse_events

FDA Adverse Event Reporting System (FAERS) reports for a specific drug. Each result describes a reported adverse reaction including patient demographics, reactions, outcome, and seriousness. Used for pharmacovigilance and post-market safety analysis.

SERVERLivedatalink SOURCEhttps://livedatalink.ai/mcp
Low RISK CLASS
Category Read
Parameters 61 required
Recommended Allowedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-blackboxfoundry-livedatalink/fda-drug-adverse-events.md

What fda_drug_adverse_events does on Livedatalink

AI agents call fda_drug_adverse_events to retrieve information from Livedatalink without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

ParameterTypeRequiredDescription
drug string Yes Drug name (brand or generic) to query FAERS for. Example: 'Lipitor' or 'atorvastatin'.
limit number Maximum rows to return (default 25, max 100).
end_date string Inclusive ISO date upper bound (YYYY-MM-DD).
reaction string Optional MedDRA-preferred-term reaction filter (e.g. 'headache', 'nausea', 'liver injury').
start_date string Inclusive ISO date lower bound (YYYY-MM-DD).
serious_only boolean If true, only return serious adverse events (death, hospitalization, life-threatening, disability).

Parameters from the server's own tool schema.

Why fda_drug_adverse_events is rated Low

This is a read-only tool that queries and retrieves historical adverse event data from a public FDA database. It does not create, modify, delete, execute commands, or transfer funds. While the data concerns drug safety and could be sensitive, the tool itself only performs information retrieval with no capability to alter records, trigger actions, or cause direct harm.

From the tool's definition Tool retrieves FDA Adverse Event Reporting System (FAERS) reports for a specific drug, describing reported adverse reactions, patient demographics, reactions, outcome, and seriousness.

Questions about fda_drug_adverse_events

What does the fda_drug_adverse_events tool do? +

FDA Adverse Event Reporting System (FAERS) reports for a specific drug. Each result describes a reported adverse reaction including patient demographics, reactions, outcome, and seriousness. Used for pharmacovigilance and post-market safety analysis. It is categorised as a Read tool in the Livedatalink MCP Server, which means it retrieves data without modifying state.

What parameters does fda_drug_adverse_events accept? +

fda_drug_adverse_events accepts 6 parameters: drug, limit, end_date, reaction, start_date, serious_only. Required: drug. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on fda_drug_adverse_events? +

Register the Livedatalink MCP server in PolicyLayer and add a rule for fda_drug_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 Livedatalink. Nothing to install.

What risk level is fda_drug_adverse_events? +

fda_drug_adverse_events is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit fda_drug_adverse_events? +

Yes. Add a rate_limit block to the fda_drug_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.

How do I block fda_drug_adverse_events completely? +

Set action: deny in the PolicyLayer policy for fda_drug_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.

What MCP server provides fda_drug_adverse_events? +

fda_drug_adverse_events is provided by the Livedatalink MCP server (https://livedatalink.ai/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

More on Livedatalink, and thousands of servers like it.

Across the catalogue

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Livedatalink's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.