Return the entities, suggested wikilinks, and new concept notes extracted from the supplied note.
AI agents call extract_entities 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 analyzes and extracts information from an existing note, performing a read-only operation. It retrieves structured data (entities, wikilinks, concepts) derived from note content without creating, modifying, or deleting any data in the vault. The analysis is informational only, making it a Read category tool with low severity.
From the tool's definition Tool 'extract_entities' returns (extracts) entities, wikilinks, and concept notes from a supplied note. The verb 'extract' and 'return' indicate data retrieval with no modification or deletion. No side effects are mentioned.
Documented attack patterns abuse exactly the kind of access extract_entities 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 extract_entities:
{
"version": "1",
"default": "deny",
"tools": {
"extract_entities": {}
}
}extract_entities 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.
Return the entities, suggested wikilinks, and new concept notes extracted from the supplied note. 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 extract_entities: 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.
extract_entities 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 extract_entities 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 extract_entities. 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.
extract_entities 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.