knowledge_base_get_crawling_status_for_latest_operation

Get crawling status for the latest operation

SERVERGhl SOURCE@aiwerk/mcp-server-ghl

Low RISK CLASS

Category Read

Parameters 32 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/aiwerk-mcp-server-ghl/knowledge-base-get-crawling-status-for-latest-operation.md

WHAT IT DOES

What knowledge_base_get_crawling_status_for_latest_operation does on Ghl

AI agents call knowledge_base_get_crawling_status_for_latest_operation to retrieve information from Ghl 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
`locationId`	string	—	Location ID as string Defaults to GHL_LOCATION_ID when omitted.
`operationId`	string	Yes	operation id as string
`knowledgeBaseId`	string	Yes	knowledge base id

Parameters from the server's own tool schema.

RISK

Why knowledge_base_get_crawling_status_for_latest_operation is rated Low

Even though knowledge_base_get_crawling_status_for_latest_operation only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs knowledge_base_get_crawling_status_for_latest_operation 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_get_crawling_status_for_latest_operation, this is the rule to start with:

knowledge_base_get_crawling_status_for_latest_operation Allowed

knowledge_base_get_crawling_status_for_latest_operation is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "knowledge_base_get_crawling_status_for_latest_operation": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Ghl, apply this rule, and every knowledge_base_get_crawling_status_for_latest_operation call is checked against it from then on.

FAQ

Questions about knowledge_base_get_crawling_status_for_latest_operation

What does the knowledge_base_get_crawling_status_for_latest_operation tool do? +

Get crawling status for the latest operation. It is categorised as a Read tool in the Ghl MCP Server, which means it retrieves data without modifying state.

What parameters does knowledge_base_get_crawling_status_for_latest_operation accept? +

knowledge_base_get_crawling_status_for_latest_operation accepts 3 parameters: locationId, operationId, knowledgeBaseId. Required: operationId, knowledgeBaseId. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on knowledge_base_get_crawling_status_for_latest_operation? +

Register the Ghl MCP server in PolicyLayer and add a rule for knowledge_base_get_crawling_status_for_latest_operation: 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.

What risk level is knowledge_base_get_crawling_status_for_latest_operation? +

knowledge_base_get_crawling_status_for_latest_operation is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit knowledge_base_get_crawling_status_for_latest_operation? +

Yes. Add a rate_limit block to the knowledge_base_get_crawling_status_for_latest_operation 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.

How do I block knowledge_base_get_crawling_status_for_latest_operation completely? +

Set action: deny in the PolicyLayer policy for knowledge_base_get_crawling_status_for_latest_operation. 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.

What MCP server provides knowledge_base_get_crawling_status_for_latest_operation? +

knowledge_base_get_crawling_status_for_latest_operation 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.

KEEP EXPLORING

More on Ghl, and thousands of servers like it.

This server

All 569 Ghl tools →

Across the catalogue

get_cocktail_by_category on Cocktails RAG MCP Server →get_file_snippet on ACE-MCP →get_torrent_detail on M-Team MCP Server →aiva_get_affiliate on AIVA MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →