get_tasks

What get_tasks does on Obsidian Elite RAG MCP Server

AI agents call get_tasks to retrieve information from Obsidian Elite RAG MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Why get_tasks is rated Low

The 'get_' prefix strongly indicates a retrieval operation with no side effects. Without explicit description, the most reasonable inference is that it queries and returns tasks from the vault. The sibling context (RAG/knowledge base system) supports a read-only data retrieval interpretation. Risk is low as no modifications, deletions, code execution, or financial operations are implied.

From the tool's definition Tool name 'get_tasks' with no description provided. Based on naming convention and sibling tools (add_memory, add_observations, analyze_*), this appears to retrieve task data from an Obsidian vault knowledge base.

The rule that runs get_tasks safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Obsidian Elite RAG MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_tasks, this is the rule to start with:

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

Questions about get_tasks