get_node_documentation
Get human-readable documentation for a node. USE THIS BEFORE get_node_info! Returns markdown with explanations, examples, auth setup, common patterns. Much easier to understand than raw schema. 87% of nodes have docs (returns
This record as markdown: /tools/aegntic-aegntic-mcp/get-node-documentation.md
What get_node_documentation does on Obsidian Elite RAG MCP Server
AI agents call get_node_documentation 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_node_documentation is rated Low
This tool retrieves and returns documentation about nodes in the knowledge base. It performs a read-only query operation that retrieves existing documentation without creating, modifying, deleting, executing code, or affecting financial data. The instruction to 'USE THIS BEFORE get_node_info' further confirms it is an informational/retrieval tool.
From the tool's definition Tool name is 'get_node_documentation' and description states it 'Returns markdown with explanations, examples, auth setup, common patterns' and 'Get human-readable documentation for a node.' These are retrieval operations with no side effects.
Attacks that exploit this kind of access
The rule that runs get_node_documentation 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_node_documentation, this is the rule to start with:
get_node_documentation is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Obsidian Elite RAG MCP Server, apply this rule, and every get_node_documentation call is checked against it from then on.
Questions about get_node_documentation
Get human-readable documentation for a node. USE THIS BEFORE get_node_info! Returns markdown with explanations, examples, auth setup, common patterns. Much easier to understand than raw schema. 87% of nodes have docs (returns. It is categorised as a Read tool in the Obsidian Elite RAG MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Obsidian Elite RAG MCP Server MCP server in PolicyLayer and add a rule for get_node_documentation: 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 Obsidian Elite RAG MCP Server. Nothing to install.
get_node_documentation 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 get_node_documentation 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 get_node_documentation. 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.
get_node_documentation is provided by the Obsidian Elite RAG MCP Server MCP server (aegntic/aegntic-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Obsidian Elite RAG MCP Server, and thousands of servers like it.
This server
Across the catalogue