Get detailed analytics for a specific Gong call — topics discussed, trackers triggered, action items, talk ratios, and speaker stats. Use gong_search_calls first to find call IDs. Args: - call_id (string): The Gong call ID - response_format (
AI agents call gong_get_call_details to retrieve information from Sales Intelligence without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and retrieves pre-recorded call metadata and analytics from Gong without creating, modifying, deleting, or executing any operations. The data is already captured; the tool simply accesses and returns it. This is a straightforward Read operation with low severity since it only exposes existing analytics data without side effects or destructive potential.
From the tool's definition Tool retrieves 'detailed analytics for a specific Gong call — topics discussed, trackers triggered, action items, talk ratios, and speaker stats.' The verb is 'Get' and the description uses passive retrieval language with no modification, creation, deletion,…
Attacks that exploit this kind of access
Get detailed analytics for a specific Gong call — topics discussed, trackers triggered, action items, talk ratios, and speaker stats. Use gong_search_calls first to find call IDs. Args: - call_id (string): The Gong call ID - response_format (. It is categorised as a Read tool in the Sales Intelligence MCP Server, which means it retrieves data without modifying state.
Register the Sales Intelligence MCP server in PolicyLayer and add a rule for gong_get_call_details: 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 Sales Intelligence. Nothing to install.
gong_get_call_details 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 gong_get_call_details 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 gong_get_call_details. 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.
gong_get_call_details is provided by the Sales Intelligence MCP server (jbalbu01/sales-intelligence-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →