health.safety.drug_events
Search FDA FAERS database for drug adverse event reports — side effects, reactions, patient demographics (OpenFDA)
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/health.safety.drug-events.md
What health.safety.drug_events does on Apibase
AI agents call health.safety.drug_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 results to skip for pagination |
limit | integer | — | Number of results (1-100, default 10) |
search | string | Yes | OpenFDA search query for adverse events (e.g. "patient.drug.medicinalproduct:aspirin", "patient.reaction.reactionmeddrapt:headache") |
Parameters from the server's own tool schema.
Why health.safety.drug_events is rated Low
Queries public adverse event data without modifying records or triggering external actions.
From the tool's definition Search FDA FAERS database for drug adverse event reports — read-only query
Attacks that exploit this kind of access
The rule that runs health.safety.drug_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 health.safety.drug_events, this is the rule to start with:
health.safety.drug_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 health.safety.drug_events call is checked against it from then on.
Questions about health.safety.drug_events
Search FDA FAERS database for drug adverse event reports — side effects, reactions, patient demographics (OpenFDA). It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
health.safety.drug_events accepts 3 parameters: skip, limit, search. Required: 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 health.safety.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 Apibase. Nothing to install.
health.safety.drug_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 health.safety.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.
Set action: deny in the PolicyLayer policy for health.safety.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.
health.safety.drug_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