This record as markdown: /tools/drausal-gohighlevel-mcp/getcalllog.md
What getCallLog does on GoHighLevel MCP Server
AI agents call getCallLog to retrieve information from GoHighLevel MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why getCallLog is rated Low
This tool retrieves call log records based on a call identifier. It performs a read-only query operation with no capacity to modify, delete, or execute actions. The blast radius is minimal—unauthorized access could expose call history data but cannot alter system state or trigger external operations. Low severity reflects the information disclosure risk typical of read operations.
From the tool's definition Tool name 'getCallLog' with description 'Returns a call log by callId' indicates a retrieval operation that queries existing data without modification or side effects.
Attacks that exploit this kind of access
The rule that runs getCallLog safely
PolicyLayer is an MCP gateway: it sits between your AI agents and GoHighLevel MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For getCallLog, this is the rule to start with:
getCallLog 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 GoHighLevel MCP Server, apply this rule, and every getCallLog call is checked against it from then on.
Questions about getCallLog
Returns a call log by callId. It is categorised as a Read tool in the GoHighLevel MCP Server MCP Server, which means it retrieves data without modifying state.
Register the GoHighLevel MCP Server MCP server in PolicyLayer and add a rule for getCallLog: 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 GoHighLevel MCP Server. Nothing to install.
getCallLog 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 getCallLog 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 getCallLog. 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.
getCallLog is provided by the GoHighLevel MCP Server MCP server (drausal/gohighlevel-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on GoHighLevel MCP Server, and thousands of servers like it.
This server
Across the catalogue