get

THE RISK

Low Risk

Why get needs a policy

This tool retrieves and queries note data from an Obsidian vault without modifying, deleting, or executing anything. The returned data (frontmatter, content, content_hash) are informational only. No destructive, financial, or code execution capabilities are present. This is a straightforward read operation with minimal blast radius if misused by an AI agent.

From the tool's definition Tool name 'get' with description 'Read a note by path. Returns frontmatter + content + content_hash.' explicitly describes retrieval of data with no side effects.

Risk signalsAdmin/system-level operation

Documented attack patterns abuse exactly the kind of access get gives an agent:

POLICY

How to control get

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 get:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "get": {}
  }
}

get is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

Create a free account and register Grove — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

CAP THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Grove tools

Destructive write_note Create, update, delete, or move notes in the vault. ACTIONS: write (default) — create o Read extract_entities Return the entities, suggested wikilinks, and new concept notes extracted from the supplie Read list_notes List notes matching a pattern. Returns path, name, type, and modified date. Use for: - C 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 Read vault_status Vault health, recent changes, and diagnostics. Modes: health — doc count, last co

All 7 Grove tools →

Read tools on other servers

M-Team MCP Server get_torrent_detail YouTube MCP Server search_channel Android Forensics ADB MCP Server parse_browser_history 0xarchive web3_challenge

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Data exfiltration → How read access becomes an exfiltration channel when chained with untrusted content.
MCP token cost → What connecting this server costs in context-window tokens on every request.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about get

What does the get tool do? +

Read a note by path. Returns frontmatter + content + content_hash. Paths are relative to vault root: e.g. It is categorised as a Read tool in the Grove MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get? +

Register the Grove MCP server in PolicyLayer and add a rule for get: 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.

What risk level is get? +

get is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get? +

Yes. Add a rate_limit block to the get 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.

How do I block get completely? +

Set action: deny in the PolicyLayer policy for get. 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.

What MCP server provides get? +

get 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.

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 →