openfda-device-events

Query openFDA medical-device adverse event reports (MAUDE).

SERVERMeta Data Mcp SOURCEpypi:meta-data-mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-derekslinz-meta-data-mcp/openfda-device-events.md

WHAT IT DOES

What openfda-device-events does on Meta Data Mcp

AI agents call openfda-device-events to retrieve information from Meta Data Mcp without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why openfda-device-events is rated Low

This tool queries an open data API (openFDA MAUDE database) to retrieve existing adverse event reports. It performs read-only data retrieval with no capability to modify, delete, or execute operations. The data is from a government open data source designed for public access. No side effects or irreversible actions are possible.

From the tool's definition Tool name 'openfda-device-events' and description 'Query openFDA medical-device adverse event reports (MAUDE)' indicate data retrieval via query operation against a public database of adverse event reports.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs openfda-device-events safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Meta Data Mcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For openfda-device-events, this is the rule to start with:

openfda-device-events Allowed

openfda-device-events is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "openfda-device-events": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Meta Data Mcp, apply this rule, and every openfda-device-events call is checked against it from then on.

FAQ

Questions about openfda-device-events

What does the openfda-device-events tool do? +

Query openFDA medical-device adverse event reports (MAUDE). It is categorised as a Read tool in the Meta Data Mcp MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on openfda-device-events? +

Register the Meta Data MCP server in PolicyLayer and add a rule for openfda-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 Meta Data Mcp. Nothing to install.

What risk level is openfda-device-events? +

openfda-device-events is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit openfda-device-events? +

Yes. Add a rate_limit block to the openfda-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.

How do I block openfda-device-events completely? +

Set action: deny in the PolicyLayer policy for openfda-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.

What MCP server provides openfda-device-events? +

openfda-device-events is provided by the Meta Data MCP server (pypi:meta-data-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Meta Data, and thousands of servers like it.

This server

All 396 Meta Data tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →