Threetone can store server configuration and tool approval records. Tool discovery is unavailable, and Test Connection is disabled. Stored approval settings do not establish live confirmation, tool-change detection, or execution enforcement.
Review the connection
1
Verify the operator and endpoint
Follow MCP server setup. Confirm the intended HTTPS endpoint and transport with the operator. Selecting I trust this server records your acknowledgement; it is not a Threetone verification of the server.
2
Limit credentials and transmitted data
Use the supported secret or auth-connection workflow. Review
secret_token, request_headers, request_meta, and auth_connection as applicable. Keep the credential’s actual permissions limited to the required actions.A secret reference avoids placing a credential in authored prose. It does not reduce the permissions held by the receiving server.3
Record approval intent
Review
approval_policy and any per-tool records. Keep an operator-supplied copy of the tool names, descriptions, and input schemas while live discovery is unavailable. Do not describe that copy as a successful connection test.4
Read back the saved resources
Use Get MCP server to inspect configuration and stored approval records. Separately inspect the intended server ID in the agent draft’s
mcp_server_ids list.Approval fields
Create MCP server tool approval stores a hash derived from the supplied name, description, and input schema. That record does not demonstrate that a future changed tool is blocked. Review changed definitions and remove obsolete approvals through the corresponding delete operation.
Frequently asked questions
Does require_approval_all guarantee a confirmation dialog?
Does require_approval_all guarantee a confirmation dialog?
No. It stores an approval policy. The actual runtime confirmation and enforcement path must be verified when execution is available.