search_location_tasks

Search tasks within a location with advanced filtering

Server GoHighLevel MCP Server keshigami/ghl-mcp-workiong
Category Read
Risk class Low
Parameters 00 required

What search_location_tasks does on GoHighLevel MCP Server

AI agents call search_location_tasks to retrieve information from GoHighLevel MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Why search_location_tasks needs a policy

This tool performs a search/query operation to retrieve task information from a location in the GoHighLevel CRM system. The use of 'search' combined with 'filtering' clearly indicates data retrieval with no side effects. No data is created, modified, deleted, or financial operations are involved. This is a straightforward Read category tool with low risk if misused by an agent.

From the tool's definition Tool name 'search_location_tasks' and description 'Search tasks within a location with advanced filtering' indicate a read-only query operation that retrieves task data without modification, deletion, or execution of external actions.

Questions about search_location_tasks

What does the search_location_tasks tool do? +

Search tasks within a location with advanced filtering. It is categorised as a Read tool in the GoHighLevel MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on search_location_tasks? +

Register the GoHighLevel MCP Server 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 GoHighLevel MCP Server. Nothing to install.

What risk level is search_location_tasks? +

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

Can I rate-limit search_location_tasks? +

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.

How do I block search_location_tasks completely? +

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.

What MCP server provides search_location_tasks? +

search_location_tasks is provided by the GoHighLevel MCP Server MCP server (keshigami/ghl-mcp-workiong). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// LOOK UP ANOTHER SERVER

Every MCP server has a record like this.

Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.