Modify nodes in the knowledge graph. This tool must be used in conjunction with list_graphs and get_node_details tools. Use cases: 1. Update basic node information (name, description, etc.) 2. Update file paths associated with nodes 3. Update node metadata information Usage recommendations: 1. F...
Accepts file system path (filePath)
Part of the Knowledge Graph Server MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.
AI agents use update_node to create or modify resources in Knowledge Graph Server. Write operations carry medium risk because an autonomous agent could trigger bulk unintended modifications. Rate limits prevent a single agent session from making hundreds of changes in rapid succession. Argument validation ensures the agent passes expected values.
Without a policy, an AI agent could call update_node repeatedly, creating or modifying resources faster than any human could review. Intercept's rate limiting ensures write operations happen at a controlled pace, and argument validation catches malformed or unexpected inputs before they reach Knowledge Graph Server.
Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.
tools:
update_node:
rules:
- action: allow
rate_limit:
max: 30
window: 60See the full Knowledge Graph Server policy for all 15 tools.
Agents calling write-class tools like update_node have been implicated in these attack patterns. Read the full case and prevention policy for each:
Other tools in the Write risk category across the catalogue. The same policy patterns (rate-limit, validate) apply to each.
Modify nodes in the knowledge graph. This tool must be used in conjunction with list_graphs and get_node_details tools. Use cases: 1. Update basic node information (name, description, etc.) 2. Update file paths associated with nodes 3. Update node metadata information Usage recommendations: 1. First call list_graphs to get target graph and node ID 2. Use get_node_details to check current node status 3. Only update fields that need to be modified, keep others unchanged 4. After updating, call get_node_details again to confirm changes Return data: - data: Updated node information * id: Node ID * name: Node name * type: Node type * description: Node description * filePath: Associated file path * metadata: Node metadata * updatedAt: Update time. It is categorised as a Write tool in the Knowledge Graph Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Add a rule in your Intercept YAML policy under the tools section for update_node. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Knowledge Graph Server MCP server.
update_node is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the update_node 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 update_node. 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.
update_node 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