Full-text BM25 search via SQLite FTS5. Best for exact-word and phrase matches.
AI agents call search_text to retrieve information from Vault Memory without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves or queries data from indexed notes using BM25 full-text search. It has no side effects—it does not create, modify, or delete content, nor does it execute code or trigger external operations. It is a pure read operation over a local knowledge base, making it a low-severity Read category tool.
From the tool's definition search_text performs full-text search via SQLite FTS5, which retrieves matching text data without modifying, deleting, or executing external operations. The description emphasizes search and phrase matching capabilities.
Attacks that exploit this kind of access
Full-text BM25 search via SQLite FTS5. Best for exact-word and phrase matches. It is categorised as a Read tool in the Vault Memory MCP Server, which means it retrieves data without modifying state.
Register the Vault Memory MCP server in PolicyLayer and add a rule for search_text: 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 Vault Memory. Nothing to install.
search_text 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_text 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_text. 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_text is provided by the Vault Memory MCP server (owrede/vault-memory). 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 →