cpsc.safety.detail
Retrieve complete details for a single CPSC recall notice by its numeric RecallID or recall number string (e.g. "26582"). Returns the full record including: product descriptions, model numbers, units affected, hazard descriptions and types, injury reports, all remedy instructions, remedy options ...
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/cpsc.safety.detail.md
What cpsc.safety.detail does on Apibase
AI agents call cpsc.safety.detail 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 |
|---|---|---|---|
recall_id | integer | — | Numeric CPSC recall ID (RecallID field). Preferred over recall_number — use the integer ID returned by cpsc.safety.search. Example: 10840. At least one of recal |
recall_number | string | — | CPSC recall number string (RecallNumber field). Typically a 5-digit string like "26582". Use when you have the recall number from a CPSC press release but not t |
Parameters from the server's own tool schema.
Why cpsc.safety.detail is rated Low
Queries public CPSC recall data without modifying, executing, or deleting information.
From the tool's definition Retrieve complete details for a single CPSC recall notice, public domain
Attacks that exploit this kind of access
The rule that runs cpsc.safety.detail 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.detail, this is the rule to start with:
cpsc.safety.detail 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.detail call is checked against it from then on.
Questions about cpsc.safety.detail
Retrieve complete details for a single CPSC recall notice by its numeric RecallID or recall number string (e.g. "26582"). Returns the full record including: product descriptions, model numbers, units affected, hazard descriptions and types, injury reports, all remedy instructions, remedy options (refund/repair/replace), manufacturer and retailer names, importer and distributor information, manufacturer country, product UPCs, and all recall images with captions. Use after cpsc.safety.search to get complete details on a specific recall record. 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.detail accepts 2 parameters: recall_id, recall_number. 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.detail: 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.detail 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.detail 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.detail. 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.detail 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