AI agents call get_call to retrieve information from Gong without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves call information from Gong's platform without creating, modifying, or deleting data. The 'Get' verb and retrieval-focused description confirm it is a Read operation.
From the tool's definition Tool name 'get_call' and description 'Get a specific Gong call' indicate retrieval of call data with no modification or deletion. The sibling tools (get_call_transcripts, get_calls, get_calls_extensive) are also retrieval operations.
Attacks that exploit this kind of access
Get a specific Gong call. It is categorised as a Read tool in the Gong MCP Server, which means it retrieves data without modifying state.
Register the Gong MCP server in PolicyLayer and add a rule for get_call: 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 Gong. Nothing to install.
get_call 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 get_call 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 get_call. 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.
get_call is provided by the Gong MCP server (micaeljarniac/gong-mcp). 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 →