search_location_tasks
Search tasks within a location with advanced filtering
This record as markdown: /tools/ghl/search-location-tasks.md
What search_location_tasks does on Ghl
AI agents call search_location_tasks 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 for pagination (default: 0) |
limit | number | — | Maximum number of tasks to return (default: 25) |
query | string | — | Search query for task content |
completed | boolean | — | Filter by completion status |
contactId | array | — | Filter by specific contact IDs |
assignedTo | array | — | Filter by assigned user IDs |
businessId | string | — | Business ID filter |
locationId | string | Yes | The location ID to search tasks in |
Parameters from the server's own tool schema.
Why search_location_tasks is rated Low
The tool performs a retrieval/query operation on tasks. 'Search' with 'filtering' indicates data retrieval only, with no side effects. No creation, modification, deletion, or execution of external code is indicated. This is a standard Read category tool.
From the tool's definition Tool name contains 'search' and description states 'Search tasks within a location with advanced filtering' — these are query operations that retrieve data without modification.
Risk signalsAccepts freeform code/query input (query)
Attacks that exploit this kind of access
The rule that runs search_location_tasks 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 search_location_tasks, this is the rule to start with:
search_location_tasks 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 search_location_tasks call is checked against it from then on.
Questions about search_location_tasks
Search tasks within a location with advanced filtering. It is categorised as a Read tool in the Ghl MCP Server, which means it retrieves data without modifying state.
search_location_tasks accepts 8 parameters: skip, limit, query, completed, contactId, assignedTo, businessId, locationId. Required: 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 search_location_tasks: 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.
search_location_tasks 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 search_location_tasks 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 search_location_tasks. 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.
search_location_tasks is provided by the Ghl MCP server (ghl-mcp-server). 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