This record as markdown: /tools/aiwerk-mcp-server-ghl/locations-task-search.md
What locations_task_search does on Ghl
AI agents call locations_task_search 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 |
|---|---|---|---|
skip | number | — | Number Of Tasks To Skip |
limit | number | — | Limit To Api |
query | string | — | Search Value |
completed | boolean | — | Task Completed Or Pending |
contactId | array | — | Contact Ids |
assignedTo | array | — | Assigned User Ids |
businessId | string | — | Bussiness Id |
locationId | string | — | Location Id Defaults to GHL_LOCATION_ID when omitted. |
Parameters from the server's own tool schema.
Why locations_task_search is rated Low
Even though locations_task_search 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
The rule that runs locations_task_search 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 locations_task_search, this is the rule to start with:
locations_task_search is read-only, so it stays allowed. 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 locations_task_search call is checked against it from then on.
Questions about locations_task_search
Task Search Filter. It is categorised as a Read tool in the Ghl MCP Server, which means it retrieves data without modifying state.
locations_task_search accepts 8 parameters: skip, limit, query, completed, contactId, assignedTo, businessId, locationId. 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 locations_task_search: 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.
locations_task_search is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the locations_task_search 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 locations_task_search. 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.
locations_task_search 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