Update details for multiple nodes at once (batch operation). Use this to efficiently modify title, description, complexity, expected output, or risks for multiple nodes in a single call. More efficient than calling update_node_detail multiple times.
AI agents use update_nodes_detail to create or update resources in Overture — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Overture environment.
This tool creates or modifies plan node metadata reversibly. It updates existing node information (title, description, complexity, expected output, risks) rather than executing external operations, deleting data, or moving money. It is a batch Write operation for metadata updates within the planning system.
From the tool's definition Tool description states it 'Update[s] details for multiple nodes' and enables modifying 'title, description, complexity, expected output, or risks.' The word 'update' and enumeration of modifiable fields (title, description, etc.) indicate data modification…
Documented attack patterns abuse exactly the kind of access update_nodes_detail gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Overture, and nothing reaches the server without passing your rules. This is the rule we recommend for update_nodes_detail:
{
"version": "1",
"default": "deny",
"tools": {
"update_nodes_detail": {
"limits": [
{
"counter": "update_nodes_detail_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}update_nodes_detail stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Update details for multiple nodes at once (batch operation). Use this to efficiently modify title, description, complexity, expected output, or risks for multiple nodes in a single call. More efficient than calling update_node_detail multiple times. It is categorised as a Write tool in the Overture MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Overture MCP server in PolicyLayer and add a rule for update_nodes_detail: 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 Overture. Nothing to install.
update_nodes_detail 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_nodes_detail 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_nodes_detail. 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_nodes_detail is provided by the Overture MCP server (sixhq/overture). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 14 Overture tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
14 Overture tools catalogued and risk-classified — across an index of 42,500+ MCP servers.