gov.fda-drug-events

FDA adverse drug event reports (FAERS). Search by drug name, optionally filter by MedDRA reaction term. Returns seriousness flags, patient demographics, reactions, drugs.

SERVERMcp SOURCE@2sio/mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-2s-io-mcp/gov.fda-drug-events.md

WHAT IT DOES

What gov.fda-drug-events does on Mcp

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

RISK

Why gov.fda-drug-events is rated Low

This tool queries and retrieves existing FDA FAERS (FDA Adverse Event Reporting System) data. The operations are read-only: searching by drug name and filtering by reaction term are data retrieval operations with no side effects. The tool returns informational results (seriousness flags, demographics, reactions) without creating, modifying, executing, deleting, or moving funds.

From the tool's definition Tool description states 'Search by drug name' and 'Returns seriousness flags, patient demographics, reactions, drugs' — purely retrieval of public FDA adverse event data with no modification, deletion, or execution capabilities.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs gov.fda-drug-events safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Mcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For gov.fda-drug-events, this is the rule to start with:

gov.fda-drug-events Allowed

gov.fda-drug-events is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "gov.fda-drug-events": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Mcp, apply this rule, and every gov.fda-drug-events call is checked against it from then on.

FAQ

Questions about gov.fda-drug-events

What does the gov.fda-drug-events tool do? +

FDA adverse drug event reports (FAERS). Search by drug name, optionally filter by MedDRA reaction term. Returns seriousness flags, patient demographics, reactions, drugs. It is categorised as a Read tool in the Mcp MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on gov.fda-drug-events? +

Register the MCP server in PolicyLayer and add a rule for gov.fda-drug-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 Mcp. Nothing to install.

What risk level is gov.fda-drug-events? +

gov.fda-drug-events is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit gov.fda-drug-events? +

Yes. Add a rate_limit block to the gov.fda-drug-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 gov.fda-drug-events completely? +

Set action: deny in the PolicyLayer policy for gov.fda-drug-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 gov.fda-drug-events? +

gov.fda-drug-events 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.

KEEP EXPLORING

More on , and thousands of servers like it.

This server

All 572 tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →