Menu

Upgrading tracehub-mcp 0.13 and cost-guard-mcp 0.6: the defaults I changed and what to set
📰

Upgrading tracehub-mcp 0.13 and cost-guard-mcp 0.6: the defaults I changed and what to set

DEV Community: security·SAI RAM·18 days ago
#7YaX2yys
#devtosecurity#devto#dev#cost#query
Reading 0:00
15s threshold

Start tracehub-mcp 0.13.0 or later with --transport http --host 0.0.0.0 and no token, and it exits with status 2. Call cost-guard-mcp 0.6.0's run_query_bounded on a query that returns 1500 rows without max_rows , and it returns status: refused with the first 1000 rows, after the query has run. The changelog calls that a billed execution, and I saw it only against a fake BigQuery client in the same process with network access blocked. Both are defaults I changed in response to an agent-run audit, and both have an opt-out.

I maintain both in the mcpsmiths GitHub org. tracehub-mcp lets an agent query traces from eight backends: Jaeger, Tempo, Traceloop, Datadog, Sentry, X-Ray, New Relic and Honeycomb. cost-guard-mcp lets an agent estimate and run queries on BigQuery, Snowflake or Databricks.…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.