openfda_adverse_events
Search FDA drug adverse event reports.
This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/openfda-adverse-events.md
What openfda_adverse_events does on UnClick
AI agents call openfda_adverse_events to retrieve information from UnClick 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 |
|---|---|---|---|
drug | string | Yes | Drug name to search adverse events for |
limit | number | — | Number of results (default 5) |
Parameters from the server's own tool schema.
Why openfda_adverse_events is rated Low
This tool retrieves historical adverse event data from public FDA databases. It performs a read-only query operation with no capability to modify records, execute code, delete data, or commit financial transactions. The data returned is informational and publicly available. Misuse would have minimal blast radius—an AI agent could retrieve irrelevant or excessive records but cannot harm systems or data integrity.
From the tool's definition Tool name contains 'Search' in description: 'Search FDA drug adverse event reports.' The verb 'search' indicates querying/retrieving data without modification or execution of external operations.
Attacks that exploit this kind of access
The rule that runs openfda_adverse_events safely
PolicyLayer is an MCP gateway: it sits between your AI agents and UnClick, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For openfda_adverse_events, this is the rule to start with:
openfda_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 UnClick, apply this rule, and every openfda_adverse_events call is checked against it from then on.
Questions about openfda_adverse_events
Search FDA drug adverse event reports. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
openfda_adverse_events accepts 2 parameters: drug, limit. Required: drug. The full parameter table on this page comes from the server's own tool schema.
Register the UnClick MCP server in PolicyLayer and add a rule for openfda_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 UnClick. Nothing to install.
openfda_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 openfda_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 openfda_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.
openfda_adverse_events is provided by the UnClick MCP server (@unclick/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on UnClick, and thousands of servers like it.
This server
Across the catalogue