This record as markdown: /tools/ghl/create-contact-task.md
What create_contact_task does on Ghl
AI agents use create_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 | Yes | Task title |
dueDate | string | Yes | 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 create_contact_task is rated Medium
Creating a task is a reversible write operation that modifies the contact's data by adding a new task record. This is not destructive (tasks can be deleted), not financial, not code execution, and not a simple read. The medium severity reflects that task creation could spam or clutter a contact's record if misused by an agent, but the impact is contained and reversible.
From the tool's definition Tool description states 'Create a new task for a contact', which is a create operation that adds new data to the system.
Risk signalsAccepts raw HTML/template content (body)
Attacks that exploit this kind of access
The rule that runs create_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 create_contact_task, this is the rule to start with:
create_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 create_contact_task call is checked against it from then on.
Questions about create_contact_task
Create a new 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.
create_contact_task accepts 6 parameters: body, title, dueDate, completed, contactId, assignedTo. Required: title, dueDate, 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 create_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.
create_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 create_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 create_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.
create_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