contacts_update_task_completed

Update Task Completed

SERVERGhl SOURCE@aiwerk/mcp-server-ghl

Medium RISK CLASS

Category Write

Parameters 33 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/aiwerk-mcp-server-ghl/contacts-update-task-completed.md

WHAT IT DOES

What contacts_update_task_completed does on Ghl

AI agents use contacts_update_task_completed 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
`contactId`	string	Yes	Contact Id

Parameters from the server's own tool schema.

RISK

Why contacts_update_task_completed is rated Medium

An AI agent can call contacts_update_task_completed faster than any human can review: one bad instruction and it creates or modifies resources in Ghl by the hundred, each call as confident as the last.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs contacts_update_task_completed 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 contacts_update_task_completed, this is the rule to start with:

contacts_update_task_completed Rate-limited

contacts_update_task_completed 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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "contacts_update_task_completed": {
      "limits": [
        {
          "counter": "contacts_update_task_completed_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Ghl, apply this rule, and every contacts_update_task_completed call is checked against it from then on.

FAQ

Questions about contacts_update_task_completed

What does the contacts_update_task_completed tool do? +

Update Task Completed. 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.

What parameters does contacts_update_task_completed accept? +

contacts_update_task_completed 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.

How do I enforce a policy on contacts_update_task_completed? +

Register the Ghl MCP server in PolicyLayer and add a rule for contacts_update_task_completed: 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.

What risk level is contacts_update_task_completed? +

contacts_update_task_completed is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit contacts_update_task_completed? +

Yes. Add a rate_limit block to the contacts_update_task_completed 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 contacts_update_task_completed completely? +

Set action: deny in the PolicyLayer policy for contacts_update_task_completed. 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 contacts_update_task_completed? +

contacts_update_task_completed is provided by the Ghl MCP server (@aiwerk/mcp-server-ghl). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Ghl, and thousands of servers like it.

This server

All 569 Ghl tools →

Across the catalogue

create_task on 0rca Dojo MCP Server →create-task on Kanban MCP Server →aroflo_create_or_update_record on AroFlo MCP → The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →