Extract keywords from note content using TF-IDF algorithm
AI agents call extract_keywords to retrieve information from Enhanced Obsidian MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a read-only operation that retrieves and processes information (keyword extraction via TF-IDF) from existing notes without creating, modifying, deleting, or executing any external operations. It has no side effects on the knowledge base. The low severity reflects minimal blast radius even if misused by an AI agent—keyword extraction cannot harm data or cause unintended effects beyond returning analyzed text.
From the tool's definition Tool extracts and analyzes keywords from existing note content using TF-IDF algorithm. The description indicates analysis of data without modification: 'extract keywords from note content'.
Documented attack patterns abuse exactly the kind of access extract_keywords gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Enhanced Obsidian MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for extract_keywords:
{
"version": "1",
"default": "deny",
"tools": {
"extract_keywords": {}
}
} extract_keywords 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.
Extract keywords from note content using TF-IDF algorithm. It is categorised as a Read tool in the Enhanced Obsidian MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Enhanced Obsidian MCP Server MCP server in PolicyLayer and add a rule for extract_keywords: 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 Enhanced Obsidian MCP Server. Nothing to install.
extract_keywords 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_keywords 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_keywords. 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_keywords is provided by the Enhanced Obsidian MCP Server MCP server (jianruidutong/obsidian-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Enhanced Obsidian MCP Server, 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.
25 Enhanced Obsidian MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.