observe-and-refresh-mqttlisted

# observe-and-refresh-mqtt Explicitly connect to a broker, observe live MQTT traffic for a short period, persist received messages, and return a fresh snapshot. This is a **control-mode** operation with real side effects. ## MCP server not available If the `topicgate` MCP server is not connected or `observe_broker_snapshot` cannot be found, stop and tell the user: > The TopicGate MCP server is not active or is running in read-only mode. > `observe_broker_snapshot` requires control mode (`--mode control`). > Install TopicGate, configure the server with `"args": ["--mode", "control"]`, > and restart your MCP harness. Do not attempt to call any other tool as a substitute. ## When to use Use only when the user explicitly intends for TopicGate to: - Activate and connect the broker - Wait for fresh traffic or retained messages - Persist the observations For passive reads of already-cached state, use `get_broker_snapshot` instead. ## Tool | Parameter | Required | Description | |---|---|---| | `broker` | yes | Broker UUID or unique case-insensitive profile name | | `topic_filter` | no | MQTT wildcard filter, default `#` (all topics) | | `max_age_seconds` | no | Omit stale values older than this threshold | | `limit` | no | Max number of topic results returned | | `payload_limit_bytes` | no | Truncate individual payloads above this size | | `wait_seconds` | no | Observation window; defaults to 1 s, capped at 5 s | ## Side effects Calling `observe_broker_snapshot`: - Change