openfda-food-enforcement

Query openFDA food enforcement (recall) records.

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-food-enforcement.md

WHAT IT DOES

What openfda-food-enforcement does on Meta Data Mcp

AI agents call openfda-food-enforcement 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-food-enforcement is rated Low

This tool queries public openFDA data about food enforcement and recalls. Querying public health records is a Read operation—it retrieves information without modifying, deleting, or executing external actions. The blast radius of misuse is minimal since the data is already public and the tool cannot issue recalls, modify records, or trigger external processes.

From the tool's definition Tool name 'openfda-food-enforcement' and description 'Query openFDA food enforcement (recall) records' indicate a retrieval operation against a public FDA database.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs openfda-food-enforcement 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-food-enforcement, this is the rule to start with:

openfda-food-enforcement Allowed

openfda-food-enforcement 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-food-enforcement": {}
  }
}

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-food-enforcement call is checked against it from then on.

FAQ

Questions about openfda-food-enforcement

What does the openfda-food-enforcement tool do? +

Query openFDA food enforcement (recall) records. 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-food-enforcement? +

Register the Meta Data MCP server in PolicyLayer and add a rule for openfda-food-enforcement: 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-food-enforcement? +

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

Can I rate-limit openfda-food-enforcement? +

Yes. Add a rate_limit block to the openfda-food-enforcement 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-food-enforcement completely? +

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

openfda-food-enforcement 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 →