diffbot.pages.analyze
Auto-detect page type (product, article, image, video) and extract structured data from any URL using AI (Diffbot)
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/diffbot.pages.analyze.md
What diffbot.pages.analyze does on Apibase
AI agents call diffbot.pages.analyze 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 | Web page URL to auto-detect type and extract structured data |
mode | string | — | Force extraction mode instead of auto-detection |
timeout | integer | — | Request timeout in milliseconds (5000-30000, default 15000) |
fallback | string | — | Fallback extraction type if auto-detection fails |
Parameters from the server's own tool schema.
Why diffbot.pages.analyze is rated Low
Tool fetches and analyzes page content without modifying data or executing code.
From the tool's definition Auto-detect page type and extract structured data from any URL
Risk signalsAccepts URL/endpoint input (url)
Attacks that exploit this kind of access
The rule that runs diffbot.pages.analyze 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.pages.analyze, this is the rule to start with:
diffbot.pages.analyze 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.pages.analyze call is checked against it from then on.
Questions about diffbot.pages.analyze
Auto-detect page type (product, article, image, video) and extract structured data from any URL using AI (Diffbot). It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
diffbot.pages.analyze accepts 4 parameters: url, mode, timeout, fallback. 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.pages.analyze: 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.pages.analyze 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.pages.analyze 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.pages.analyze. 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.pages.analyze 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