Query the FDA FAERS adverse event reports database. Returns drug-event records with patient demographics, drug names, reaction terms (MedDRA-coded), outcomes, and seriousness flags. Uses openFDA Lucene-style search syntax (e.g. "patient.drug.medicinalproduct:aspirin"). License: openFDA CC0 1.0 Un...
AI agents call query_fda_drug_events to retrieve information from TensorFeed without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
skip | number | — | Pagination offset (0-25000) |
sort | string | — | Sort by field (e.g. receivedate:desc) |
limit | number | — | Max records to return (1-100) |
search | string | — | openFDA Lucene-style search expression. Examples: patient.drug.medicinalproduct:aspirin, patient.reaction.reactionmeddrapt:headache+AND+receivedate:[20240101+TO |
Parameters from the server's own tool schema.
This tool retrieves and searches publicly available FDA adverse event data without any ability to modify, delete, or execute operations. It is a straightforward read operation that queries a database and returns results. The public nature of the data (openFDA with CC0 licensing) and read-only semantics place it clearly in the Read category with low severity.
From the tool's definition Tool description states it 'Query[s] the FDA FAERS adverse event reports database' and 'Returns drug-event records' — these are read-only retrieval operations with no modification, deletion, or execution capabilities.
Attacks that exploit this kind of access
Query the FDA FAERS adverse event reports database. Returns drug-event records with patient demographics, drug names, reaction terms (MedDRA-coded), outcomes, and seriousness flags. Uses openFDA Lucene-style search syntax (e.g. "patient.drug.medicinalproduct:aspirin"). License: openFDA CC0 1.0 Universal Dedication, FDA waiver of all copyright; commercial redistribution permitted. It is categorised as a Read tool in the TensorFeed MCP Server, which means it retrieves data without modifying state.
query_fda_drug_events accepts 4 parameters: skip, sort, limit, search. The full parameter table on this page comes from the server's own tool schema.
Register the TensorFeed MCP server in PolicyLayer and add a rule for query_fda_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 TensorFeed. Nothing to install.
query_fda_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 query_fda_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 query_fda_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.
query_fda_drug_events is provided by the TensorFeed MCP server (https://mcp.tensorfeed.ai/mcp). 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 →