get_node_info
Get COMPLETE technical schema for a node. WARNING: Returns massive JSON (often 100KB+) with all properties, operations, credentials. Contains duplicates and complex conditional logic. TIPS: 1) Use get_node_essentials first for common use cases, 2) Try get_node_documentation for human-readable inf...
This record as markdown: /tools/aegntic-aegntic-mcp/get-node-info.md
What get_node_info does on Obsidian Elite RAG MCP Server
AI agents call get_node_info 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_info is rated Low
The tool retrieves and returns data (technical schemas, properties, credentials) without modifying, deleting, or executing operations. It is categorized as Read. However, severity is elevated to 'high' because the tool explicitly exposes 'credentials' and sensitive technical configurations in its output, creating risk if an AI agent queries nodes containing secrets or security-sensitive information.
From the tool's definition Tool name 'get_node_info' with description stating it 'Get[s] COMPLETE technical schema for a node' and 'Returns massive JSON...with all properties, operations, credentials.' This is a retrieval operation that queries and exposes node metadata and…
Attacks that exploit this kind of access
The rule that runs get_node_info 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_info, this is the rule to start with:
get_node_info 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_info call is checked against it from then on.
Questions about get_node_info
Get COMPLETE technical schema for a node. WARNING: Returns massive JSON (often 100KB+) with all properties, operations, credentials. Contains duplicates and complex conditional logic. TIPS: 1) Use get_node_essentials first for common use cases, 2) Try get_node_documentation for human-readable info, 3) Look for. 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_info: 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_info 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_info 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_info. 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_info 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