This record as markdown: /tools/aiwerk-mcp-server-ghl/voice-ai-get-call-logs.md
What voice_ai_get_call_logs does on Ghl
AI agents call voice_ai_get_call_logs 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 |
|---|---|---|---|
page | number | — | Page number (1-based). |
sort | string | — | Sort direction. Applies only when sortBy is provided. |
sortBy | string | — | Field to sort by. Defaults to newest if omitted. |
agentId | string | — | Agent identifier. When provided, returns logs for this agent only. |
endDate | number | — | End date filter (Unix timestamp). Must be greater than startDate. Both startDate and endDate must be provided together. |
callType | string | — | Call type filter. |
pageSize | number | — | Page size (max 50). |
contactId | string | — | Contact IDs (comma-separated) to filter by. |
startDate | number | — | Start date filter (Unix timestamp). Must be less than endDate. Both startDate and endDate must be provided together. |
actionType | string | — | Action type filter for call logs (comma-separated ACTION_TYPE values) |
locationId | string | — | Location identifier. Filters results to this location. Defaults to GHL_LOCATION_ID when omitted. |
Parameters from the server's own tool schema.
Why voice_ai_get_call_logs is rated Low
Even though voice_ai_get_call_logs only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Risk signalsHigh parameter count (11 properties)
Attacks that exploit this kind of access
The rule that runs voice_ai_get_call_logs 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 voice_ai_get_call_logs, this is the rule to start with:
voice_ai_get_call_logs is read-only, so it stays allowed. 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 voice_ai_get_call_logs call is checked against it from then on.
Questions about voice_ai_get_call_logs
List Call Logs. It is categorised as a Read tool in the Ghl MCP Server, which means it retrieves data without modifying state.
voice_ai_get_call_logs accepts 11 parameters: page, sort, sortBy, agentId, endDate, callType, pageSize, contactId, startDate, actionType, locationId. 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 voice_ai_get_call_logs: 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.
voice_ai_get_call_logs is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the voice_ai_get_call_logs 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 voice_ai_get_call_logs. 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.
voice_ai_get_call_logs 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.
More on Ghl, and thousands of servers like it.
This server
Across the catalogue