Find Gong calls where a specific person participated, identified by their email address. Useful for pulling a prospect
AI agents call gong_search_calls_by_participant 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 retrieves historical call data based on email address lookup. It is a pure read operation (search/find) that queries an existing dataset. The blast radius of misuse is low—an agent could potentially search for calls involving unintended people, but this only exposes information that already exists within the Gong system for authorized users; it does not create, modify, or destroy data, nor does it trigger…
From the tool's definition Tool description states 'Find Gong calls where a specific person participated' - a search/query operation that retrieves call records without modifying or deleting data. No side effects described.
Attacks that exploit this kind of access
Find Gong calls where a specific person participated, identified by their email address. Useful for pulling a prospect. 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_search_calls_by_participant: 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_search_calls_by_participant 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_search_calls_by_participant 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_search_calls_by_participant. 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_search_calls_by_participant 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 →