Skip to content

Commit b9ae4a1

Browse files
committed
docs: update CHANGELOG for v1.4.0
Correct release date and document the Phase 1 read-only query tools (query_sql, query_influxql, list_tables, describe_table, investigate_database), QuerySafetyService, TelemetryService, and two related fixes (query routing options, outer query limits).
1 parent 4447448 commit b9ae4a1

1 file changed

Lines changed: 11 additions & 1 deletion

File tree

CHANGELOG.md

Lines changed: 11 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -5,16 +5,26 @@ All notable changes to the official InfluxDB MCP Server will be documented in th
55
The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
66
and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
77

8-
## [1.4.0] - 2026-06-05
8+
## [1.4.0] - 2026-07-30
99

1010
### Added
1111

12+
- **Read-only query tools** (Phase 1): `query_sql`, `query_influxql`, `list_tables`, `describe_table`, and `investigate_database`, each enforcing read-only access at the tool boundary
13+
- New `QuerySafetyService` validates queries against an allow list (`SELECT`, `SHOW`, `EXPLAIN`, `WITH` for SQL; `SELECT`, `SHOW` for InfluxQL) and rejects write/DDL statements before they reach InfluxDB
14+
- Row limit enforcement: default 1000 rows, hard max 5000, applied consistently across query paths including outer-query limits on wrapped queries
15+
- Query routing options forwarded through to the underlying query execution (e.g. per-request timeout, query parameters)
16+
- New `TelemetryService` logs tool-boundary events (request id, query id, duration, row count, truncation, success/error code) to a local telemetry file
1217
- **Enterprise/Core Retention Policy Support**: Added database retention policy configuration for Core/Enterprise instances via `update_database` tool
1318
- New method `updateDatabaseCoreEnterprise()` in `DatabaseManagementService` for PUT `/api/v3/configure/database`
1419
- Support for `retentionPeriod` parameter on Core/Enterprise (sent as `retention_period`, a humantime duration string such as `"60d"`)
1520
- Warning when unsupported parameters (maxTables, maxColumnsPerTable) are provided for Core/Enterprise
1621
- Enhanced tool description to indicate Core/Enterprise support for retention configuration
1722

23+
### Fixed
24+
25+
- Query routing options (timeout, parameters) are now forwarded correctly instead of being dropped
26+
- Outer query limits are now enforced on wrapped/nested queries, not just top-level queries
27+
1828
### Enhanced
1929

2030
- **Tool Availability**: Updated `update_database` from "Cloud Dedicated only" to "All versions"

0 commit comments

Comments
 (0)