libi.analysis_search_transcript
Substring search over transcript words. Returns ±2-word context windows around each hit with start/end timestamps.
This record as markdown: /tools/libi/libi.analysis-search-transcript.md
What libi.analysis_search_transcript does on Libi
AI agents call libi.analysis_search_transcript to retrieve information from Libi without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why libi.analysis_search_transcript is rated Low
Tool queries and retrieves transcript data without modifying, executing code, or causing irreversible effects.
From the tool's definition Substring search over transcript words. Returns context windows with timestamps.
Attacks that exploit this kind of access
The rule that runs libi.analysis_search_transcript safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Libi, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For libi.analysis_search_transcript, this is the rule to start with:
libi.analysis_search_transcript is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Libi, apply this rule, and every libi.analysis_search_transcript call is checked against it from then on.
Questions about libi.analysis_search_transcript
Substring search over transcript words. Returns ±2-word context windows around each hit with start/end timestamps. It is categorised as a Read tool in the Libi MCP Server, which means it retrieves data without modifying state.
Register the Libi MCP server in PolicyLayer and add a rule for libi.analysis_search_transcript: 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 Libi. Nothing to install.
libi.analysis_search_transcript 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 libi.analysis_search_transcript 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 libi.analysis_search_transcript. 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.
libi.analysis_search_transcript is provided by the Libi MCP server (Nagellabs/libi). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Libi, and thousands of servers like it.
This server
Across the catalogue