diffbot.articles.extract
Extract article text, author, date, tags, sentiment, and images from any blog or news URL with multi-page support (Diffbot)
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/diffbot.articles.extract.md
What diffbot.articles.extract does on Apibase
AI agents call diffbot.articles.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 | Article or blog post URL to extract text, author, and metadata |
paging | boolean | — | Follow multi-page articles and concatenate text (default true) |
maxTags | integer | — | Maximum number of topic tags to return (1-50, default 10) |
timeout | integer | — | Request timeout in milliseconds (5000-30000, default 15000) |
Parameters from the server's own tool schema.
Why diffbot.articles.extract is rated Low
Tool retrieves publicly available article metadata and content without modification or side effects.
From the tool's definition Extract article text, author, date, tags, sentiment, and images from URL
Risk signalsAccepts URL/endpoint input (url)
Attacks that exploit this kind of access
The rule that runs diffbot.articles.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.articles.extract, this is the rule to start with:
diffbot.articles.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.articles.extract call is checked against it from then on.
Questions about diffbot.articles.extract
Extract article text, author, date, tags, sentiment, and images from any blog or news URL with multi-page support (Diffbot). It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
diffbot.articles.extract accepts 4 parameters: url, paging, maxTags, timeout. 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.articles.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.articles.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.articles.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.articles.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.articles.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