This record as markdown: /tools/ghl/update-contact-task.md
What update_contact_task does on Ghl
AI agents use update_contact_task 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 |
|---|---|---|---|
body | string | — | Task description |
title | string | — | Task title |
taskId | string | Yes | Task ID |
dueDate | string | — | Due date (ISO format) |
completed | boolean | — | Task completion status |
contactId | string | Yes | Contact ID |
assignedTo | string | — | User ID to assign task to |
Parameters from the server's own tool schema.
Why update_contact_task is rated Medium
This tool creates or modifies data in a reversible manner (tasks can be updated again or deleted), which aligns with the Write category. It does not execute arbitrary code, delete data irreversibly, or involve financial transactions. The severity is medium because task updates in a CRM system could affect business workflows or contact management, but the impact is localized and reversible.
From the tool's definition Tool name 'update_contact_task' and description 'Update a task for a contact' indicate modification of existing task data associated with a contact record.
Risk signalsAccepts raw HTML/template content (body)
Attacks that exploit this kind of access
The rule that runs update_contact_task 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_contact_task, this is the rule to start with:
update_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 Ghl, apply this rule, and every update_contact_task call is checked against it from then on.
Questions about update_contact_task
Update a task for a contact. 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_contact_task accepts 7 parameters: body, title, taskId, dueDate, completed, contactId, assignedTo. Required: taskId, 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_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 Ghl. Nothing to install.
update_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 update_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 update_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.
update_contact_task 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