openfda_devices.reference.classification
Search FDA medical device classification database — 7,000+ product codes with risk class and regulatory requirements. Returns device name, product code, device class (1=low/exempt, 2=moderate/510k, 3=high/PMA), medical specialty, regulation number, definition, life-sustain/implant flags. Filter b...
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/openfda-devices.reference.classification.md
What openfda_devices.reference.classification does on Apibase
AI agents call openfda_devices.reference.classification to retrieve information from Apibase 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 |
|---|---|---|---|
skip | integer | — | Number of records to skip for pagination (default 0). |
limit | integer | — | Number of records to return (1–99, default 10). |
search | string | — | OpenFDA search expression using Lucene syntax. Single field: device_name:"pacemaker" or recall_status:"Ongoing". Combined: device_name:"insulin pump"+AND+recall |
Parameters from the server's own tool schema.
Why openfda_devices.reference.classification is rated Low
Tool queries public FDA device classification data without modifying, deleting, or executing operations.
From the tool's definition Search FDA database, returns device name, product code, classification. Filter by name, code, class, specialty.
Attacks that exploit this kind of access
The rule that runs openfda_devices.reference.classification safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Apibase, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For openfda_devices.reference.classification, this is the rule to start with:
openfda_devices.reference.classification 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 Apibase, apply this rule, and every openfda_devices.reference.classification call is checked against it from then on.
Questions about openfda_devices.reference.classification
Search FDA medical device classification database — 7,000+ product codes with risk class and regulatory requirements. Returns device name, product code, device class (1=low/exempt, 2=moderate/510k, 3=high/PMA), medical specialty, regulation number, definition, life-sustain/implant flags. Filter by device name, product code, device class, or specialty description. Device class determines the regulatory pathway: Class I (General Controls), Class II (510k), Class III (PMA). Source: FDA CDRH device classification database, US public domain. It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
openfda_devices.reference.classification accepts 3 parameters: skip, limit, search. The full parameter table on this page comes from the server's own tool schema.
Register the Apibase MCP server in PolicyLayer and add a rule for openfda_devices.reference.classification: 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 Apibase. Nothing to install.
openfda_devices.reference.classification 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_devices.reference.classification 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_devices.reference.classification. 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_devices.reference.classification is provided by the Apibase MCP server (apibase-mcp-client). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Apibase, and thousands of servers like it.
This server
Across the catalogue