get_contact_tasks

Get all tasks for a contact

SERVERGhl SOURCEghl-mcp-server

Low RISK CLASS

Category Read

Parameters 11 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/ghl/get-contact-tasks.md

WHAT IT DOES

What get_contact_tasks does on Ghl

AI agents call get_contact_tasks to retrieve information from Ghl without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Parameter	Type	Required	Description
`contactId`	string	Yes	Contact ID

Parameters from the server's own tool schema.

RISK

Why get_contact_tasks is rated Low

This tool queries and retrieves existing task data associated with a contact. It performs a GET-like operation that does not create, modify, delete, or execute any operations. The action is read-only and non-destructive, making it a Read category tool with low severity.

From the tool's definition Tool name 'get_contact_tasks' and description 'Get all tasks for a contact' indicate data retrieval with no modification or side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

get_contact_tasks Allowed

get_contact_tasks is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_contact_tasks": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about get_contact_tasks

What does the get_contact_tasks tool do? +

Get all tasks for a contact. It is categorised as a Read tool in the Ghl MCP Server, which means it retrieves data without modifying state.

What parameters does get_contact_tasks accept? +

get_contact_tasks accepts 1 parameter: contactId. Required: contactId. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on get_contact_tasks? +

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

get_contact_tasks is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_contact_tasks? +

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

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

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

KEEP EXPLORING

More on Ghl, and thousands of servers like it.

This server

All 253 Ghl tools →

Across the catalogue

get_cocktail_by_category on Cocktails RAG MCP Server →get_torrent_detail on M-Team MCP Server →aiva_get_affiliate on AIVA MCP Server →get-chuck-categories on Jokes MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →