Update the status of a node during execution. Use this to show progress as you work through the plan. The node will visually update on the canvas.
AI agents use update_node_status 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 data in a reversible manner by updating node status fields. It does not execute arbitrary code, delete data irreversibly, or move money. While it affects the visual representation of plan execution, the underlying state change is non-destructive and can be reversed by subsequent status updates.
From the tool's definition The tool 'update_node_status' modifies the status field of a node during execution, causing visual updates on the canvas. The verb 'Update' and the description 'Update the status of a node' indicate a write operation that changes existing data.
Documented attack patterns abuse exactly the kind of access update_node_status 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_node_status:
{
"version": "1",
"default": "deny",
"tools": {
"update_node_status": {
"limits": [
{
"counter": "update_node_status_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}update_node_status 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 the status of a node during execution. Use this to show progress as you work through the plan. The node will visually update on the canvas. 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_node_status: 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_node_status 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_status 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_status. 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_status 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.