// MCP TOOL REFERENCE

GROVE TOOLS

7 tools from the Grove MCP Server, categorised by risk level.

// ALL 7 GROVE TOOLS

READ 6 tools

Read extract_entities Return the entities, suggested wikilinks, and new concept notes extracted from the supplied note. Read get Read a note by path. Returns frontmatter + content + content_hash. Paths are relative to vault root: e.g. Read list_notes List notes matching a pattern. Returns path, name, type, and modified date. Use for: - Check if a note ex... Read multi_get Read multiple notes at once. Accepts a glob pattern or comma-separated paths. Examples: Read query Search notes by keyword or meaning. Returns ranked results with snippets. Sub-query types: lex — BM25 ke... Read vault_status Vault health, recent changes, and diagnostics. Modes: health — doc count, last commit date histo...

DESTRUCTIVE 1 tools

Destructive write_note Create, update, delete, or move notes in the vault. ACTIONS: write (default) — create or update a note (...

// FAQ

How many tools does the Grove MCP server have? +

The Grove MCP server exposes 7 tools across 2 categories: Read, Destructive.

How do I enforce policies on Grove tools? +

Route the Grove server through the PolicyLayer gateway. Define allow, deny, or approval rules per tool in the dashboard; they are enforced on every call before it reaches the server.

What risk categories do Grove tools fall into? +

Grove tools are categorised as Read (6), Destructive (1). Each category has a recommended default policy.

Enforce policy on every Grove tool call.

Start from Grove, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →

Free to start. No card required.

43,000+ MCP servers and 220,000+ tools scanned and risk-classified.