AI agents call transcript_search to retrieve information from Cortex without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool appears to search through transcripts stored in the Cortex memory system, consistent with the server's role in persisting and retrieving session data. Search operations are read-only queries with no capability to modify, delete, or execute external actions.
From the tool's definition Tool name 'transcript_search' combined with server context describing a memory/knowledge vault system suggests querying or retrieving transcript data. The tool name uses the read-pattern verb 'search'. No description provided, which lowers confidence.
Documented attack patterns abuse exactly the kind of access transcript_search gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Cortex, and nothing reaches the server without passing your rules. This is the rule we recommend for transcript_search:
{
"version": "1",
"default": "deny",
"tools": {
"transcript_search": {}
}
}transcript_search is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
transcript_search. It is categorised as a Read tool in the Cortex MCP Server, which means it retrieves data without modifying state.
Register the Cortex MCP server in PolicyLayer and add a rule for transcript_search: 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 Cortex. Nothing to install.
transcript_search 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 transcript_search 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 transcript_search. 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.
transcript_search is provided by the Cortex MCP server (tt-wang/memem). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 14 Cortex tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
14 Cortex tools catalogued and risk-classified — across an index of 42,500+ MCP servers.