@proof-holdings/mcp-server

Official

Overview Schema Source Related Servers Discussions Admin

update_hitl

Destructive

Update a human-in-the-loop configuration by changing its name, notification channels, or timeout. Use it to keep approval workflows routed to the right contacts and time limits.

Instructions

Update a HITL config. Can change name, channels, or timeout.

ACCESS: needs a Proof account. Set PROOF_API_KEY and restart this server, then call this tool again. start_login does NOT open this tool.

Input Schema

Name	Required	Description
`id`	Yes	HITL config ID
`name`	No	New name (null to clear)
`channels`	No	Updated channels
`timeout_seconds`	No	Updated timeout in seconds (60–86400)

Output Schema

Name	Required	Description
`id`	Yes	MongoDB ObjectId
`name`	No
`status`	Yes	Status of a HITL configuration
`keypair`	Yes	Encryption keypair metadata (null if not configured)
`user_id`	Yes	Owner user ID (useful for SDK encryption AAD)
`channels`	Yes
`circle_id`	No	Backing Circle for a circle-backed Approvals config (null for channel-list configs)
`created_at`	Yes
`profile_id`	No
`updated_at`	Yes
`environment`	Yes
`timeout_seconds`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedv1.7.2Nov 6, 2026

removedInput schema / additionalProperties
```
Removed value: -false
```

removedInput schema / properties / channels / items / anyOf

Removed value: -[
-  {
-    "additionalProperties": false,
-    "properties": {
-      "config": {
-        "additionalProperties": false,
-        "properties": {
-          "chat_id": {
-            "maxLength": 50,
-            "minLength": 1,
-            "type": "string"
-          }
-        },
-        "required": [
-          "chat_id"
-        ],
-        "type": "object"
-      },
-      "type": {
-        "const": "telegram",
-        "type": "string"
-      }
-    },
-    "required": [
-      "type",
-      "config"
-    ],
-    "type": "object"
-  },
-  {
-    "additionalProperties": false,
-    "properties": {
-      "config": {
-        "additionalProperties": false,
-        "properties": {
-          "bsuid": {
-            "description": "WhatsApp Business-Scoped User ID (e.g. US.abc123...)",
-            "pattern": "^[A-Z]{2}\\.[a-zA-Z0-9]{10,140}$",
-            "type": "string"
-          },
-          "phone_number": {
-            "description": "Phone number in E.164 format",
-            "pattern": "^\\+?[1-9]\\d{6,14}$",
-            "type": "string"
-          }
-        },
-        "type": "object"
-      },
-      "type": {
-        "const": "whatsapp",
-        "type": "string"
-      }
-    },
-    "required": [
-      "type",
-      "config"
-    ],
-    "type": "object"
-  }
-]

addedInput schema / properties / channels / items / oneOf

Added value: +[
+  {
+    "properties": {
+      "config": {
+        "properties": {
+          "chat_id": {
+            "maxLength": 50,
+            "minLength": 1,
+            "type": "string"
+          }
+        },
+        "required": [
+          "chat_id"
+        ],
+        "type": "object"
+      },
+      "type": {
+        "const": "telegram",
+        "type": "string"
+      }
+    },
+    "required": [
+      "type",
+      "config"
+    ],
+    "type": "object"
+  },
+  {
+    "properties": {
+      "config": {
+        "properties": {
+          "bsuid": {
+            "description": "WhatsApp Business-Scoped User ID (e.g. US.abc123...)",
+            "pattern": "^[A-Z]{2}\\.[a-zA-Z0-9]{10,140}$",
+            "type": "string"
+          },
+          "phone_number": {
+            "description": "Phone number in E.164 format",
+            "pattern": "^\\+?[1-9]\\d{6,14}$",
+            "type": "string"
+          }
+        },
+        "type": "object"
+      },
+      "type": {
+        "const": "whatsapp",
+        "type": "string"
+      }
+    },
+    "required": [
+      "type",
+      "config"
+    ],
+    "type": "object"
+  }
+]

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": {},
+  "description": "HITL configuration with messaging channels and timeout",
+  "properties": {
+    "channels": {
+      "items": {
+        "oneOf": [
+          {
+            "additionalProperties": {},
+            "properties": {
+              "config": {
+                "additionalProperties": {},
+                "properties": {
+                  "chat_id": {
+                    "type": "string"
+                  }
+                },
+                "required": [
+                  "chat_id"
+                ],
+                "type": "object"
+              },
+              "type": {
+                "const": "telegram",
+                "type": "string"
+              }
+            },
+            "required": [
+              "type",
+              "config"
+            ],
+            "type": "object"
+          },
+          {
+            "additionalProperties": {},
+            "properties": {
+              "config": {
+                "additionalProperties": {},
+                "properties": {
+                  "bsuid": {
+                    "type": "string"
+                  },
+                  "phone_number": {
+                    "type": "string"
+                  }
+                },
+                "type": "object"
+              },
+              "type": {
+                "const": "whatsapp",
+                "type": "string"
+              }
+            },
+            "required": [
+              "type",
+              "config"
+            ],
+            "type": "object"
+          }
+        ]
+      },
+      "type": "array"
+    },
+    "circle_id": {
+      "description": "Backing Circle for a circle-backed Approvals config (null for channel-list configs)",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "created_at": {
+      "type": "string"
+    },
+    "environment": {
+      "type": "string"
+    },
+    "id": {
+      "description": "MongoDB ObjectId",
+      "type": "string"
+    },
+    "keypair": {
+      "anyOf": [
+        {
+          "additionalProperties": {},
+          "properties": {
+            "has_backup_wrapper": {
+              "type": "boolean"
+            },
+            "has_encrypted_private_key": {
+              "type": "boolean"
+            },
+            "has_wrapped_dek": {
+              "type": "boolean"
+            },
+            "kid": {
+              "type": "string"
+            }
+          },
+          "required": [
+            "kid",
+            "has_encrypted_private_key",
+            "has_wrapped_dek",
+            "has_backup_wrapper"
+          ],
+          "type": "object"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "description": "Encryption keypair metadata (null if not configured)"
+    },
+    "name": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "profile_id": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "status": {
+      "description": "Status of a HITL configuration",
+      "type": "string"
+    },
+    "timeout_seconds": {
+      "maximum": 9007199254740991,
+      "minimum": -9007199254740991,
+      "type": "integer"
+    },
+    "updated_at": {
+      "type": "string"
+    },
+    "user_id": {
+      "description": "Owner user ID (useful for SDK encryption AAD)",
+      "type": [
+        "string",
+        "null"
+      ]
+    }
+  },
+  "required": [
+    "id",
+    "user_id",
+    "channels",
+    "timeout_seconds",
+    "status",
+    "keypair",
+    "environment",
+    "created_at",
+    "updated_at"
+  ],
+  "type": "object"
+}

First observedv1.1.0Sep 9, 2026

TDQS

B3.4/5.0

Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint=false and destructiveHint=true, and the description adds genuinely useful non-schema context about the API-key prerequisite. However, it never explains what the destructive aspect is — notably whether passing 'channels' replaces the entire channel list or merges with it, and whether omitted fields are left untouched. For a mutation tool flagged destructive, that omission is a real gap.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short blocks, front-loaded with the core action before the access caveat, with no filler sentences. The ACCESS paragraph is operational rather than descriptive, but it earns its place by preventing a likely failed call.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so return values need no explanation, and all four parameters are documented in the schema. What remains missing is the mutation's effect model — replace vs merge for channels, and confirmation of whether this is a partial update — which matters given the destructiveHint.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%: 'id', null-to-clear on 'name', channel shapes, and the 60–86400 timeout range are all documented in the schema. The description only restates the field list, adding no patch-vs-replace semantics or interpretation of null/omitted values beyond what the schema already says.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

Names a specific verb and resource ('Update a HITL config') and enumerates the mutable fields (name, channels, timeout), which distinguishes it from create_hitl/get_hitl/delete_hitl among the siblings. It stops short of explicitly naming those siblings as alternatives.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The tool is implied to operate on an existing config identified by 'id', and the ACCESS block tells the agent a Proof account plus PROOF_API_KEY is required and that start_login does not unlock this tool. That is authentication guidance, not when-to-use guidance: there is no statement of exclusions or pointers to create_hitl/get_hitl for adjacent tasks.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server