complete_contact_task
Set the completed status of a contact's task
This record as markdown: /tools/basicmachines-co-open-ghl-mcp/complete-contact-task.md
What complete_contact_task does on GoHighLevel MCP Server
AI agents use complete_contact_task to create or update resources in GoHighLevel MCP Server, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your GoHighLevel MCP Server environment.
Why complete_contact_task is rated Medium
This tool updates task status to 'completed', a reversible modification of data. It does not delete or destroy the task, execute external code, move money, or retrieve data. A contact task status update is a standard write operation. Severity is low because task completion is a benign, expected business operation with minimal risk even if triggered inappropriately by an AI agent.
From the tool's definition Tool description: 'Set the completed status of a contact's task' — modifies the status property of an existing task record.
Attacks that exploit this kind of access
The rule that runs complete_contact_task safely
PolicyLayer is an MCP gateway: it sits between your AI agents and GoHighLevel MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For complete_contact_task, this is the rule to start with:
complete_contact_task stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect GoHighLevel MCP Server, apply this rule, and every complete_contact_task call is checked against it from then on.
Questions about complete_contact_task
Set the completed status of a contact's task. It is categorised as a Write tool in the GoHighLevel MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the GoHighLevel MCP Server MCP server in PolicyLayer and add a rule for complete_contact_task: 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.
complete_contact_task is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the complete_contact_task 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 complete_contact_task. 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.
complete_contact_task is provided by the GoHighLevel MCP Server MCP server (basicmachines-co/open-ghl-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on GoHighLevel MCP Server, and thousands of servers like it.
This server
Across the catalogue