Query the FDA MAUDE medical device adverse event reports database. Returns device identifiers, problem codes, event narratives, patient outcomes. Useful for safety signal detection on FDA-cleared devices. License: openFDA CC0 1.0; commercial redistribution permitted.
AI agents call query_fda_device_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 |
limit | number | — | Max records to return (1-100) |
search | string | — | openFDA Lucene-style search expression. Examples: device.brand_name:medtronic, device.generic_name:pacemaker |
Parameters from the server's own tool schema.
This is a read-only tool that retrieves historical adverse event data from a public FDA database. It has no side effects—it cannot modify records, execute code, delete data, or trigger external operations. The severity is low because the data is public and already published; an agent querying this information presents minimal risk.
From the tool's definition Tool performs a query operation ("Query the FDA MAUDE") that retrieves data ("Returns device identifiers, problem codes, event narratives, patient outcomes"). No modification, deletion, execution, or financial operations described.
Attacks that exploit this kind of access
Query the FDA MAUDE medical device adverse event reports database. Returns device identifiers, problem codes, event narratives, patient outcomes. Useful for safety signal detection on FDA-cleared devices. License: openFDA CC0 1.0; 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_device_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_device_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_device_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_device_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_device_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_device_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 →