Search consumer product recalls from the CPSC (Consumer Product Safety Commission) database. Covers toys, electronics, furniture, appliances, children's products, tools, and clothing — everything under CPSC jurisdiction. Does NOT cover food/drugs (FDA), motor vehicles/tires (NHTSA), boats (USCG),...
Risk signalsBulk/mass operation — affects multiple targets
Part of the Cpsc Recalls Mcp Server server.
Free to start. No card required.
AI agents call cpsc_search_recalls to retrieve information from Cpsc Recalls Mcp Server without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.
Even though cpsc_search_recalls only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.
Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.
{
"version": "1",
"default": "deny",
"tools": {
"cpsc_search_recalls": {}
}
}See the full Cpsc Recalls Mcp Server policy for all 3 tools.
These attack patterns abuse exactly the kind of access cpsc_search_recalls gives an agent. Each links to the full case and the policy that stops it:
Other read tools across the catalogue. The same approach applies to each: allow, with a rate cap to control cost.
Search consumer product recalls from the CPSC (Consumer Product Safety Commission) database. Covers toys, electronics, furniture, appliances, children's products, tools, and clothing — everything under CPSC jurisdiction. Does NOT cover food/drugs (FDA), motor vehicles/tires (NHTSA), boats (USCG), or pesticides (EPA). All filter fields are optional substring matches that combine with AND. For hazard-type filtering ("fire", "choking", "burn"), use description_search — the dedicated Hazard filter is non-functional in the upstream API. When manufacturer returns no results, try importer or retailer: many recalls list the importer or retailer as the primary responsible org. Use cpsc_get_recall with a recall_number from results to retrieve the full record including complete description, all images, and incident reports.. It is categorised as a Read tool in the Cpsc Recalls Mcp Server MCP Server, which means it retrieves data without modifying state.
Register the Cpsc Recalls Mcp Server MCP server in PolicyLayer and add a rule for cpsc_search_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 Cpsc Recalls Mcp Server. Nothing to install.
cpsc_search_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 cpsc_search_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 cpsc_search_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.
cpsc_search_recalls is provided by the Cpsc Recalls Mcp Server MCP server (@cyanheads/cpsc-recalls-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 3 Cpsc Recalls Mcp Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
4,600+ MCP servers and 31,000+ tools scanned and risk-classified.