scrape_knowledge_url
Fetch a URL's content into the knowledge base. Server crawls the URL, stores the response body in R2, returns the new document ID. Failures store the row with status='failed'. Use for adding marketing pages, FAQ docs, or external references the agent should be aware of.
This record as markdown: /tools/io-favcrm-favcrm/scrape-knowledge-url.md
What scrape_knowledge_url does on FavCRM
AI agents use scrape_knowledge_url to create or update resources in FavCRM, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your FavCRM environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
url | string | Yes | URL to fetch (must be https / http and publicly reachable) |
Parameters from the server's own tool schema.
Why scrape_knowledge_url is rated Medium
This tool fetches external URL content and writes it into the knowledge base (stored in R2 object storage). It creates a new document record, which is a reversible write operation. The severity is medium because a malicious or erroneous URL could pollute the knowledge base with harmful or misleading content that an AI agent may later rely upon, but the action itself is not irreversible (records can be deleted).
From the tool's definition Fetch a URL's content into the knowledge base... stores the response body in R2, returns the new document ID
Risk signalsAccepts URL/endpoint input (url)
Attacks that exploit this kind of access
The rule that runs scrape_knowledge_url safely
PolicyLayer is an MCP gateway: it sits between your AI agents and FavCRM, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For scrape_knowledge_url, this is the rule to start with:
scrape_knowledge_url stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect FavCRM, apply this rule, and every scrape_knowledge_url call is checked against it from then on.
Questions about scrape_knowledge_url
Fetch a URL's content into the knowledge base. Server crawls the URL, stores the response body in R2, returns the new document ID. Failures store the row with status='failed'. Use for adding marketing pages, FAQ docs, or external references the agent should be aware of. It is categorised as a Write tool in the FavCRM MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
scrape_knowledge_url accepts 1 parameter: url. Required: url. The full parameter table on this page comes from the server's own tool schema.
Register the FavCRM MCP server in PolicyLayer and add a rule for scrape_knowledge_url: 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 FavCRM. Nothing to install.
scrape_knowledge_url is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the scrape_knowledge_url 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 scrape_knowledge_url. 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.
scrape_knowledge_url is provided by the FavCRM MCP server (https://api.favcrm.io/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on FavCRM, and thousands of servers like it.
This server
Across the catalogue