fda_openfda.safety.food_adverse_events
Search the FDA CAERS database of consumer-reported adverse events for foods and dietary supplements. Returns reported reactions, outcomes (hospitalization, death, etc.), implicated product names and industry, and consumer demographics (age, gender). Filter using Lucene syntax: products.industry_n...
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/fda-openfda.safety.food-adverse-events.md
What fda_openfda.safety.food_adverse_events does on Apibase
AI agents call fda_openfda.safety.food_adverse_events to retrieve information from Apibase 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 |
|---|---|---|---|
skip | integer | — | Number of records to skip for pagination (default 0). |
limit | integer | — | Number of records to return (1–99, default 10). |
search | string | — | OpenFDA search expression using Lucene syntax. Single field: brand_name:"tylenol" or classification:"Class I". Combined: generic_name:"ibuprofen"+AND+dosage_for |
Parameters from the server's own tool schema.
Why fda_openfda.safety.food_adverse_events is rated Low
Tool queries public health data; no modification, deletion, or execution capabilities present.
From the tool's definition Search FDA CAERS database, returns consumer-reported adverse events data
Attacks that exploit this kind of access
The rule that runs fda_openfda.safety.food_adverse_events safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Apibase, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For fda_openfda.safety.food_adverse_events, this is the rule to start with:
fda_openfda.safety.food_adverse_events is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Apibase, apply this rule, and every fda_openfda.safety.food_adverse_events call is checked against it from then on.
Questions about fda_openfda.safety.food_adverse_events
Search the FDA CAERS database of consumer-reported adverse events for foods and dietary supplements. Returns reported reactions, outcomes (hospitalization, death, etc.), implicated product names and industry, and consumer demographics (age, gender). Filter using Lucene syntax: products.industry_name:"Vit/Min/Prot/Unconv Diet(Human/Animal)" or reactions:"NAUSEA". Distinct from food recall enforcement (health.food_enforcement) — this covers consumer-reported illness/injury, not manufacturer recalls. Source: FDA CAERS database, US public domain. It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
fda_openfda.safety.food_adverse_events accepts 3 parameters: skip, limit, search. The full parameter table on this page comes from the server's own tool schema.
Register the Apibase MCP server in PolicyLayer and add a rule for fda_openfda.safety.food_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 Apibase. Nothing to install.
fda_openfda.safety.food_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 fda_openfda.safety.food_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 fda_openfda.safety.food_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.
fda_openfda.safety.food_adverse_events is provided by the Apibase MCP server (apibase-mcp-client). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Apibase, and thousands of servers like it.
This server
Across the catalogue