This record as markdown: /tools/aiwerk-mcp-server-ghl/knowledge-base-delete-trained-urls-for-knowledge-base.md
What knowledge_base_delete_trained_urls_for_knowledge_base does on Ghl
AI agents call knowledge_base_delete_trained_urls_for_knowledge_base to permanently remove resources in Ghl, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
| Parameter | Type | Required | Description |
|---|---|---|---|
urlIds | array | Yes | List of trained urls ids ( fetched from the Get all trained page links by knowledge base endpoint) |
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_delete_trained_urls_for_knowledge_base is rated Critical
An AI agent that decides to call knowledge_base_delete_trained_urls_for_knowledge_base doesn't hesitate, doesn't double-check, and doesn't stop at one. Whatever it removes from Ghl is gone. There is no undo for destructive operations.
Attacks that exploit this kind of access
The rule that runs knowledge_base_delete_trained_urls_for_knowledge_base 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_delete_trained_urls_for_knowledge_base, this is the rule to start with:
knowledge_base_delete_trained_urls_for_knowledge_base is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Ghl, apply this rule, and every knowledge_base_delete_trained_urls_for_knowledge_base call is checked against it from then on.
Questions about knowledge_base_delete_trained_urls_for_knowledge_base
Delete trained pages. It is categorised as a Destructive tool in the Ghl MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
knowledge_base_delete_trained_urls_for_knowledge_base accepts 3 parameters: urlIds, locationId, knowledgeBaseId. Required: urlIds, 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_delete_trained_urls_for_knowledge_base: 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_delete_trained_urls_for_knowledge_base is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the knowledge_base_delete_trained_urls_for_knowledge_base 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_delete_trained_urls_for_knowledge_base. 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_delete_trained_urls_for_knowledge_base 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.
Across the catalogue