mureo_state_settings_set
Switch ops history on for this workspace (settings.ops_history.enabled in STATE.json; off by default). When on, every change-making tool must carry reason and expected, and a proposed / adopted mureo_decision_record must declare…
Instructions
Switch ops history on for this workspace (settings.ops_history.enabled in STATE.json; off by default). When on, every change-making tool must carry reason and expected, and a proposed / adopted mureo_decision_record must declare expected. Only true is accepted: switching it off is done by the operator in mureo configure. Use it only when the operator asks. Returns the stored settings.
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"ops_history_enabled": "<ops_history_enabled>"
},
"name": "mureo_state_settings_set"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| path | No | Optional path to STATE.json. Defaults to STATE.json in the MCP server's current working directory. Paths outside it are refused. | |
| reason | No | Why this change is being made: one or two sentences naming the evidence and the expected effect. Stored in the journal and on the action_log entry this call produces, for the operator and the next session. | |
| ops_history_enabled | Yes | true. Switching off is refused here. |