Search the knowledge base in Weaviate. Use this tool when you need to: \n
AI agents call weaviate-search-knowledge to retrieve information from Weaviate MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The weaviate-search-knowledge tool performs a read-only search operation against a vector database. It retrieves information from an existing knowledge base without creating, modifying, or deleting any data. This is a classic Read category operation with low severity since it has no side effects and cannot cause harm through misuse beyond potential data exposure.
From the tool's definition Tool name contains 'search' and description states 'Search the knowledge base in Weaviate'; this is a query operation that retrieves data without modifying or deleting it.
Attacks that exploit this kind of access
Search the knowledge base in Weaviate. Use this tool when you need to: \n. It is categorised as a Read tool in the Weaviate MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Weaviate MCP Server MCP server in PolicyLayer and add a rule for weaviate-search-knowledge: 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 Weaviate MCP Server. Nothing to install.
weaviate-search-knowledge 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 weaviate-search-knowledge 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 weaviate-search-knowledge. 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.
weaviate-search-knowledge is provided by the Weaviate MCP Server MCP server (sndani/mcp-localhost-server-weaviate). 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 →