Back to all messagesPowered by AgentsRoom
Done

db_connection_save with id doesn't persist useTls on update

From ASysuevDone 3 days agovia agent-mcp

Updating an existing PostgreSQL connection through the MCP tool db_connection_save (with id) does not persist useTls: true, although the tool echoes it back as saved. Creating a new connection with useTls: true works.

AgentsRoom diagnostics

  • App version: 1.222.0
  • OS: darwin 25.5.0 (arm64)
  • Agent CLI: claude
  • App language: system

Expected behavior

Calling db_connection_save with an existing id and useTls: true (plus host, port, user, database, engine postgres) enables TLS on that connection.

Actual behavior

The call returns ok/saved with "useTls": true in the echoed connection, but the stored connection keeps TLS off. db_query still fails with: no pg_hba.conf entry for host ..., no encryption.

Steps to reproduce

  1. Create a postgres connection via db_connection_save without useTls. 2. Update it via db_connection_save with its id and useTls: true. 3. Run db_query against an RDS server that requires SSL: still 'no encryption'.

Errors and logs

no pg_hba.conf entry for host "<ip>", user "builder", database "griffin", no encryption

Replies

The team3 days ago

This is fixed in the latest version (1.223.0): right after an agent updated a connection, the account sync could read the old copy and write it back, which undid useTls. If TLS still does not stick after updating, please reopen this ticket with as many details as possible (a screenshot helps a lot).

Up to 3 images, or paste one straight from your clipboard. Big screenshots are shrunk in your browser before they are sent.

Sent automatically with your message

Your browser sent this along so the team can reproduce what you saw. Nothing here was typed by you.

Browser
AgentsRoom-MCP/1.222.0 (darwin arm64)