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. Fi...
Risk signalsAccepts file system path (filePath)
Part of the Knowledge Graph Server server.
Free to start. No card required.
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. PolicyLayer'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.
{
"version": "1",
"default": "deny",
"tools": {
"update_node": {
"limits": [
{
"counter": "update_node_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}See the full Knowledge Graph Server policy for all 15 tools.
These attack patterns abuse exactly the kind of access update_node gives an agent. Each links to the full case and the policy that stops it:
Other write tools across the catalogue. The same approach applies to each: rate-limit and validate the arguments.
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.
Register the Knowledge Graph Server MCP server in PolicyLayer and add a rule for update_node: 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 Knowledge Graph Server. Nothing to install.
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 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 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). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 15 Knowledge Graph Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
4,600+ MCP servers and 31,000+ tools scanned and risk-classified.