Section-level retrieval. Composes the v1 hybrid (semantic + BM25 + RRF) pipeline with
AI agents call search_sections 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 searches and retrieves data from notes without creating, modifying, deleting, or executing anything. It is a pure query/retrieval function with no side effects, fitting the Read category. The low severity reflects that retrieving knowledge from local notes carries minimal blast radius unless the notes themselves contain sensitive data (which is a data classification issue, not a tool-level one).
From the tool's definition Tool name is 'search_sections' and description indicates 'Section-level retrieval' using a 'hybrid (semantic + BM25 + RRF) pipeline' — standard information retrieval operations with no modification, deletion, or execution of code.
Attacks that exploit this kind of access
Section-level retrieval. Composes the v1 hybrid (semantic + BM25 + RRF) pipeline with. 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_sections: 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_sections 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_sections 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_sections. 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_sections 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 →