Search LiveKit documentation
AI agents call search_documentation to retrieve information from LiveKit RAG Assistant without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs semantic search over documentation using Pinecone vector search. Searching is a read-only operation that retrieves existing data with no ability to modify, delete, or execute code. The operation is confined to querying a documentation index, making it a straightforward Read category tool with low severity and low blast radius if misused by an AI agent.
From the tool's definition Tool name 'search_documentation' and description 'Search LiveKit documentation' indicate a query operation that retrieves information without modification or side effects.
Attacks that exploit this kind of access
Search LiveKit documentation. It is categorised as a Read tool in the LiveKit RAG Assistant MCP Server, which means it retrieves data without modifying state.
Register the LiveKit RAG Assistant MCP server in PolicyLayer and add a rule for search_documentation: 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 LiveKit RAG Assistant. Nothing to install.
search_documentation 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_documentation 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_documentation. 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_documentation is provided by the LiveKit RAG Assistant MCP server (thenabilman/thenabilman_livekit_mcp_assistant). 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 →