awslabs.postgres-mcp-server: --readonly flag not honored

[jritsema]

Describe the bug

The server doesn't appear to be honoring the --readonly argument when asked to update a record. According to the model:

I notice that in the configuration file, the --readonly parameter is actually set to "False", which should allow write operations. However, it seems there might be a discrepancy between the configuration and the actual behavior of the MCP server.

Config:

{
    "awslabs-aurora-postgres": {
      "command": "uvx",
      "args": [
        "awslabs.postgres-mcp-server@latest",
        "--resource_arn",
        "arn:aws:rds:us-east-1:...",
        "--secret_arn",
        "arn:aws:secretsmanager:us-east-1:...",
        "--database",
        "postgres",
        "--readonly",
        "False",
        "--region",
        "us-east-1"
      ],
      "env": {
        "AURORA_POSTGRES_ARN": "arn:aws:rds:us-east-1:...",
        "AURORA_POSTGRES_DATABASE": "postgres",
        "AURORA_POSTGRES_SECRET_ARN": "arn:aws:secretsmanager:us-east-1:..."
      }
    }
}

Expected Behavior

Setting --readonly False (I believe I tried --readonly false as well) should allow updates/inserts/delets.

Current Behavior

I apologize for the issue. It seems that the Aurora PostgreSQL tool is currently configured in read-only mode, which prevents us from making updates to the database.

Reproduction Steps

See above

Possible Solution

No response

Additional Information/Context

No response

OS

MacOS M4

Server

other

Server Version

No response

Region experiencing the issue

us-east-1

Other information

No response

Service quota

• I have reviewed the service quotas for this construct

[ChenKuanSun]

Same here