fda_device_recalls
FDA medical device recalls. Filter by device name or recalling manufacturer, classification (Class 1 most severe), or date range. Used for medical device supply chain monitoring and hospital biomed compliance.
This record as markdown: /tools/io-github-blackboxfoundry-livedatalink/fda-device-recalls.md
What fda_device_recalls does on Livedatalink
AI agents call fda_device_recalls to retrieve information from Livedatalink 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 |
|---|---|---|---|
limit | number | — | Maximum rows to return (default 25, max 100). |
query | string | — | Optional device name or recalling firm search term. |
end_date | string | — | Inclusive ISO date upper bound (YYYY-MM-DD). |
start_date | string | — | Inclusive ISO date lower bound (YYYY-MM-DD). |
classification | string | — | Recall classification: 1 (Class I, most severe), 2, 3. |
Parameters from the server's own tool schema.
Why fda_device_recalls is rated Low
Even though fda_device_recalls only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Attacks that exploit this kind of access
The rule that runs fda_device_recalls safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Livedatalink, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For fda_device_recalls, this is the rule to start with:
fda_device_recalls 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 Livedatalink, apply this rule, and every fda_device_recalls call is checked against it from then on.
Questions about fda_device_recalls
FDA medical device recalls. Filter by device name or recalling manufacturer, classification (Class 1 most severe), or date range. Used for medical device supply chain monitoring and hospital biomed compliance. It is categorised as a Read tool in the Livedatalink MCP Server, which means it retrieves data without modifying state.
fda_device_recalls accepts 5 parameters: limit, query, end_date, start_date, classification. The full parameter table on this page comes from the server's own tool schema.
Register the Livedatalink MCP server in PolicyLayer and add a rule for fda_device_recalls: 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 Livedatalink. Nothing to install.
fda_device_recalls 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_device_recalls 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_device_recalls. 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_device_recalls is provided by the Livedatalink MCP server (https://livedatalink.ai/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Livedatalink, and thousands of servers like it.
This server
Across the catalogue