cpsc.safety.search
Search US Consumer Product Safety Commission (CPSC) recall notices by product name, product category, manufacturer, date range, hazard type, and country of origin. Returns matching recalls with title, description, hazards, remedy options, manufacturer details, and official recall URL from cpsc.go...
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/cpsc.safety.search.md
What cpsc.safety.search does on Apibase
AI agents call cpsc.safety.search 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 |
|---|---|---|---|
limit | integer | — | Maximum number of recalls to return (1–100, default 20). The API may match more records — use date_start/date_end to narrow results. |
hazard | string | — | Hazard type keyword to filter recalls. Must match an exact CPSC hazard name. Example: "fire hazard", "choking hazard". Note: use product_name or product_type fo |
country | string | — | Manufacturer country of origin to filter recalls. Example: "China", "United States", "Vietnam". |
date_end | string | — | End date for recall date range filter (ISO 8601 format YYYY-MM-DD). Example: "2024-12-31". Only returns recalls issued on or before this date. |
date_start | string | — | Start date for recall date range filter (ISO 8601 format YYYY-MM-DD). Example: "2024-01-01". Only returns recalls issued on or after this date. |
manufacturer | string | — | Manufacturer or brand name to filter recalls (partial match). Example: "Fisher-Price", "IKEA", "Honda". |
product_name | string | — | Product name keyword to filter recalls (partial match). Example: "bicycle helmet", "smoke detector", "baby carrier". |
product_type | string | — | CPSC product category to filter recalls. Common values: "Toys", "Clothing", "Furniture", "Sports & Recreation", "Home Furnishings", "Electronics", "Children's P |
Parameters from the server's own tool schema.
Why cpsc.safety.search is rated Low
Tool queries publicly available safety recall database without modification or side effects.
From the tool's definition Search CPSC recall notices, returns matching recalls, no auth, public domain data
Attacks that exploit this kind of access
The rule that runs cpsc.safety.search 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 cpsc.safety.search, this is the rule to start with:
cpsc.safety.search 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 cpsc.safety.search call is checked against it from then on.
Questions about cpsc.safety.search
Search US Consumer Product Safety Commission (CPSC) recall notices by product name, product category, manufacturer, date range, hazard type, and country of origin. Returns matching recalls with title, description, hazards, remedy options, manufacturer details, and official recall URL from cpsc.gov. Database contains all recalls since 1974 — over 6 000 active recall records. Use to check whether a specific product or brand has been recalled for safety defects, fire hazards, choking risks, or other consumer safety issues. No auth — US Consumer Product Safety Act public domain data, unlimited free. It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
cpsc.safety.search accepts 8 parameters: limit, hazard, country, date_end, date_start, manufacturer, product_name, product_type. 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 cpsc.safety.search: 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.
cpsc.safety.search 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.safety.search 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.safety.search. 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.safety.search 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