Get FDA adverse event reports for a drug from the openFDA database.
AI agents call fda_adverse_events to retrieve information from MCP Healthcare Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves historical adverse event reports from a public FDA database. It performs a query operation with no side effects—no data is created, modified, deleted, or executed. The tool enables lookup of existing medical safety information, which is characteristic of Read category operations.
From the tool's definition Tool description explicitly states 'Get FDA adverse event reports' which is a retrieval operation from the openFDA database.
Attacks that exploit this kind of access
Get FDA adverse event reports for a drug from the openFDA database. It is categorised as a Read tool in the MCP Healthcare Server MCP Server, which means it retrieves data without modifying state.
Register the MCP Healthcare Server 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 MCP Healthcare Server. Nothing to install.
fda_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_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_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_adverse_events is provided by the MCP Healthcare Server MCP server (shinegami-2002/mcp-healthcare-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →