crow_browser_extract_article
Extract a (possibly paywalled) article by trying a fallback ladder: live page → archive.today → Wayback → 12ft.io. Each candidate is loaded IN the stealth browser and parsed with Readability, then quality-gated. Returns the first clean result, tagged with the method that won.
This record as markdown: /tools/kh0pper-crow/crow-browser-extract-article.md
What crow_browser_extract_article does on Crow
AI agents invoke crow_browser_extract_article to trigger actions in Crow. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
Why crow_browser_extract_article is rated High
This tool actively runs a stealth browser, executes page loads across multiple external services (including paywall-bypass services like 12ft.io), and processes the results. This is an external operation whose effects depend on arguments, placing it firmly in Execute. The paywall-bypass capability adds reputational/legal risk, raising severity to medium.
From the tool's definition 'loaded IN the stealth browser' and 'trying a fallback ladder: live page → archive.today → Wayback → 12ft.io' — triggers external browser operations and network requests to multiple external services
Attacks that exploit this kind of access
The rule that runs crow_browser_extract_article safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Crow, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For crow_browser_extract_article, this is the rule to start with:
crow_browser_extract_article stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Crow, apply this rule, and every crow_browser_extract_article call is checked against it from then on.
Questions about crow_browser_extract_article
Extract a (possibly paywalled) article by trying a fallback ladder: live page → archive.today → Wayback → 12ft.io. Each candidate is loaded IN the stealth browser and parsed with Readability, then quality-gated. Returns the first clean result, tagged with the method that won. It is categorised as a Execute tool in the Crow MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Crow MCP server in PolicyLayer and add a rule for crow_browser_extract_article: 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 Crow. Nothing to install.
crow_browser_extract_article is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the crow_browser_extract_article 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 crow_browser_extract_article. 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.
crow_browser_extract_article is provided by the Crow MCP server (kh0pper/crow). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Crow, and thousands of servers like it.
This server
Across the catalogue