diffbot.products.extract
Extract structured product data from any e-commerce URL — title, price, brand, specs, images, reviews. Works on any retailer without custom integration (Diffbot)
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/diffbot.products.extract.md
What diffbot.products.extract does on Apibase
AI agents call diffbot.products.extract 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 |
|---|---|---|---|
url | string | Yes | Product page URL to extract data from (any e-commerce site) |
timeout | integer | — | Request timeout in milliseconds (5000-30000, default 15000) |
discussion | boolean | — | Include product reviews and comments (default false) |
Parameters from the server's own tool schema.
Why diffbot.products.extract is rated Low
Retrieves and extracts publicly available product information from e-commerce websites without modification or side effects.
From the tool's definition Extract structured product data from any e-commerce URL — title, price, brand, specs, images, reviews.
Risk signalsAccepts URL/endpoint input (url)
Attacks that exploit this kind of access
The rule that runs diffbot.products.extract 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 diffbot.products.extract, this is the rule to start with:
diffbot.products.extract 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 diffbot.products.extract call is checked against it from then on.
Questions about diffbot.products.extract
Extract structured product data from any e-commerce URL — title, price, brand, specs, images, reviews. Works on any retailer without custom integration (Diffbot). It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
diffbot.products.extract accepts 3 parameters: url, timeout, discussion. Required: url. 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 diffbot.products.extract: 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.
diffbot.products.extract 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 diffbot.products.extract 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 diffbot.products.extract. 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.
diffbot.products.extract 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