fda_adverse_events

SERVERScorpTech x402 API SOURCEhttps://scorptech.it.com/api/x402/mcp

Low RISK CLASS

Category Read

Parameters 120 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/com-it-scorptech-x402/fda-adverse-events.md

WHAT IT DOES

What fda_adverse_events does on ScorpTech x402 API

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

Parameter	Type	Required	Description
`to`	string	—	on/before YYYY-MM-DD
`drug`	string	—	drug: brand / generic / reported name
`from`	string	—	on/after YYYY-MM-DD
`full`	boolean	—	full openFDA records (default false)
`skip`	integer	—	offset 0-25000
`sort`	string	—	field:asc\|desc
`count`	string	—	count by this field (e.g. patient.reaction.reactionmeddrapt.exact)
`limit`	integer	—	1-100 (default 10); count 1-1000
`search`	string	—	raw openFDA search, ANDed
`product`	string	—	device or food product name
`serious`	boolean	—	drug: serious reports only (true/false)
`category`	string	—	drug (default), device or food

Parameters from the server's own tool schema.

RISK

Why fda_adverse_events is rated Low

Even though fda_adverse_events only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.

Risk signalsHigh parameter count (13 properties)

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs fda_adverse_events safely

PolicyLayer is an MCP gateway: it sits between your AI agents and ScorpTech x402 API, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For fda_adverse_events, this is the rule to start with:

fda_adverse_events Allowed

fda_adverse_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": {
    "fda_adverse_events": {}
  }
}

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

The button opens the PolicyLayer dashboard: create your workspace, connect ScorpTech x402 API, apply this rule, and every fda_adverse_events call is checked against it from then on.

FAQ

Questions about fda_adverse_events

What does the fda_adverse_events tool do? +

FDA adverse-event reports (openFDA): drug FAERS, device MAUDE, food/supplement CAERS. Filter by drug, product, reaction, dates or raw openFDA search; compact reports or counts on any field (e.g. top reactions for a drug). Price: $0.01 USDC per successful call (x402, Solana). Same tool over HTTPS: GET https://scorptech.it.com/api/x402/v1/fda-adverse-events. It is categorised as a Read tool in the ScorpTech x402 API MCP Server, which means it retrieves data without modifying state.

What parameters does fda_adverse_events accept? +

fda_adverse_events accepts 12 parameters: to, drug, from, full, skip, sort, count, limit, search, product, serious, category. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on fda_adverse_events? +

Register the ScorpTech x402 API MCP server in PolicyLayer and add a rule for fda_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 ScorpTech x402 API. Nothing to install.

What risk level is fda_adverse_events? +

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

Can I rate-limit fda_adverse_events? +

Yes. Add a rate_limit block to the fda_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_adverse_events completely? +

Set action: deny in the PolicyLayer policy for fda_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_adverse_events? +

fda_adverse_events is provided by the ScorpTech x402 API MCP server (https://scorptech.it.com/api/x402/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on ScorpTech x402 API, and thousands of servers like it.

This server

All 1012 ScorpTech x402 API tools →

Across the catalogue

The MCP Attack Database →

Guides

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