Get detailed information about a specific node in the graph. This tool must be used in conjunction with the list_graphs tool, as the nodeId must be obtained from the list_graphs response. Use cases: 1. View complete node attributes 2. Check associated resources (SVG/Markdown) 3. Analyze node rela...
Single-target operation
Part of the Knowledge Graph Server MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.
AI agents call get_node_details to retrieve information from Knowledge Graph Server without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.
Even though get_node_details only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.
Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.
tools:
get_node_details:
rules:
- action: allowSee the full Knowledge Graph Server policy for all 15 tools.
Agents calling read-class tools like get_node_details have been implicated in these attack patterns. Read the full case and prevention policy for each:
Other tools in the Read risk category across the catalogue. The same policy patterns (rate-limit, allow) apply to each.
Get detailed information about a specific node in the graph. This tool must be used in conjunction with the list_graphs tool, as the nodeId must be obtained from the list_graphs response. Use cases: 1. View complete node attributes 2. Check associated resources (SVG/Markdown) 3. Analyze node relationships with others 4. Check current state before modifying a node Usage recommendations: 1. First call list_graphs to get the node list of the target graph 2. Get the required nodeId from the returned nodes array 3. Use the obtained graphId and nodeId to call this tool 4. Check the returned relationship data to determine if further action is needed Return data: - data: Node details * id: Node ID * name: Node name * type: Node type * description: Node description * filePath: Associated file path * metadata: Node metadata * resources: Associated resource list - id: Resource ID - type: Resource type (svg/markdown) - title: Resource title * relationships: Relationship list - id: Edge ID - type: Edge type - targetNode: Target node information. It is categorised as a Read tool in the Knowledge Graph Server MCP Server, which means it retrieves data without modifying state.
Add a rule in your Intercept YAML policy under the tools section for get_node_details. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Knowledge Graph Server MCP server.
get_node_details 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_details rule in your Intercept 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 Intercept policy for get_node_details. 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_details is provided by the Knowledge Graph Server MCP server (aiuluna/knowledge-graph-mcp). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Open source. One binary. Zero dependencies.
npx -y @policylayer/intercept