AI agents call gov.fda-food-recalls to retrieve information from Mcp without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries publicly available FDA enforcement data without creating, modifying, deleting, executing code, or committing financial transactions. It is a straightforward read-only information lookup tool. The low severity reflects minimal blast radius if misused—an AI agent cannot cause harm by querying food recall records.
From the tool's definition Tool provides "FDA food recall enforcement reports" with filtering capabilities by product name, classification, status, and recalling-firm state. The verbs 'reports' and 'filter' indicate data retrieval with no modification or side effects.
Attacks that exploit this kind of access
FDA food recall enforcement reports, newest first. Filter by product name, classification, status, recalling-firm state. It is categorised as a Read tool in the Mcp MCP Server, which means it retrieves data without modifying state.
Register the MCP server in PolicyLayer and add a rule for gov.fda-food-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 Mcp. Nothing to install.
gov.fda-food-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 gov.fda-food-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 gov.fda-food-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.
gov.fda-food-recalls is provided by the MCP server (@2sio/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 →