This record as markdown: /tools/ghl/update-task-completion.md
What update_task_completion does on Ghl
AI agents use update_task_completion to create or update resources in Ghl, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Ghl environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
taskId | string | Yes | Task ID |
completed | boolean | Yes | Completion status |
contactId | string | Yes | Contact ID |
Parameters from the server's own tool schema.
Why update_task_completion is rated Medium
This tool modifies existing task records by changing their completion status. It is a Write operation because it updates data reversibly—task completion status can be toggled or changed back. The severity is medium because misuse could mark tasks as complete when they are not, potentially disrupting workflow management, but the impact is typically reversible and scoped to task records.
From the tool's definition Tool name is 'update_task_completion' and description states 'Update task completion status', indicating modification of task data.
Attacks that exploit this kind of access
The rule that runs update_task_completion 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 update_task_completion, this is the rule to start with:
update_task_completion 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 Ghl, apply this rule, and every update_task_completion call is checked against it from then on.
Questions about update_task_completion
Update task completion status. It is categorised as a Write tool in the Ghl MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
update_task_completion accepts 3 parameters: taskId, completed, contactId. Required: taskId, completed, contactId. 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 update_task_completion: 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.
update_task_completion 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 update_task_completion 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 update_task_completion. 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.
update_task_completion 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