Semantic search over customer-interview transcripts.
AI agents call search_interviews to retrieve information from Gq Insight without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries existing interview data and returns search results. It does not create, modify, delete, or execute code. The operation is purely informational retrieval with no capability to alter data or trigger external side effects. Low severity reflects minimal blast radius if misused — an AI agent could only retrieve available interview content.
From the tool's definition Tool description states it performs "Semantic search over customer-interview transcripts" — a retrieval operation with no side effects. The server context emphasizes "grounded answering" and traceability, consistent with read-only query functionality.
Attacks that exploit this kind of access
Semantic search over customer-interview transcripts. It is categorised as a Read tool in the Gq Insight MCP Server, which means it retrieves data without modifying state.
Register the Gq Insight MCP server in PolicyLayer and add a rule for search_interviews: 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 Gq Insight. Nothing to install.
search_interviews 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 search_interviews 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 search_interviews. 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.
search_interviews is provided by the Gq Insight MCP server (yusufdxb/gq-insight-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 →