Search notes by keyword or meaning. Returns ranked results with snippets. Sub-query types: lex — BM25 keyword search (exact terms, fast) vec — semantic vector search (meaning-based) Always provide intent to disambiguate. Combine lex + vec for best results. Example: searches=[{type:
AI agents call query to retrieve information from Grove without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries data from an Obsidian vault without creating, modifying, deleting, or executing operations. It is a pure read operation that returns search results with no side effects. The blast radius of misuse is minimal—an AI agent could retrieve sensitive notes but cannot alter or destroy data.
From the tool's definition Tool description states 'Search notes by keyword or meaning. Returns ranked results with snippets.' The sub-query types (lex and vec) perform keyword and semantic searches with no modification capability.
Documented attack patterns abuse exactly the kind of access query gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Grove, and nothing reaches the server without passing your rules. This is the rule we recommend for query:
{
"version": "1",
"default": "deny",
"tools": {
"query": {}
}
}query is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Search notes by keyword or meaning. Returns ranked results with snippets. Sub-query types: lex — BM25 keyword search (exact terms, fast) vec — semantic vector search (meaning-based) Always provide intent to disambiguate. Combine lex + vec for best results. Example: searches=[{type:. It is categorised as a Read tool in the Grove MCP Server, which means it retrieves data without modifying state.
Register the Grove MCP server in PolicyLayer and add a rule for query: 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 Grove. Nothing to install.
query 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 query 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 query. 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.
query is provided by the Grove MCP server (jmilinovich/grove). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Grove, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
7 Grove tools catalogued and risk-classified — across an index of 43,000+ MCP servers.