This record as markdown: /tools/aiwerk-mcp-server-ghl/knowledge-base-discover-website.md
What knowledge_base_discover_website does on Ghl
AI agents invoke knowledge_base_discover_website to trigger actions in Ghl. 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.
| Parameter | Type | Required | Description |
|---|---|---|---|
url | string | Yes | Website URL as string |
option | string | Yes | Mode as string |
locationId | string | — | Location ID as string Defaults to GHL_LOCATION_ID when omitted. |
knowledgeBaseId | string | Yes | knowledge base ID as string |
Parameters from the server's own tool schema.
Why knowledge_base_discover_website is rated High
knowledge_base_discover_website triggers real processes with real consequences. An agent gone sideways doesn't fire it once. It starts dozens of builds, sends mass notifications, or burns through compute before anyone looks up.
Risk signalsAccepts URL/endpoint input (url)
Attacks that exploit this kind of access
The rule that runs knowledge_base_discover_website safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Ghl, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For knowledge_base_discover_website, this is the rule to start with:
knowledge_base_discover_website 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 Ghl, apply this rule, and every knowledge_base_discover_website call is checked against it from then on.
Questions about knowledge_base_discover_website
Start crawling and discover pages for training. It is categorised as a Execute tool in the Ghl MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
knowledge_base_discover_website accepts 4 parameters: url, option, locationId, knowledgeBaseId. Required: url, option, knowledgeBaseId. The full parameter table on this page comes from the server's own tool schema.
Register the Ghl MCP server in PolicyLayer and add a rule for knowledge_base_discover_website: 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 Ghl. Nothing to install.
knowledge_base_discover_website 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 knowledge_base_discover_website 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 knowledge_base_discover_website. 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.
knowledge_base_discover_website is provided by the Ghl MCP server (@aiwerk/mcp-server-ghl). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Ghl, and thousands of servers like it.
This server
Across the catalogue