Skip to main content
September 9, 2026 Running a Bolt schedule from an AI client and changing what that run actually does are two different things, so the MCP server now treats them as two tools with two permissions. The override tool is filtered out of the tool list entirely for roles that do not hold the new permission, so their AI client never sees an override parameter to fill in, and the same roles keep triggering schedules exactly as before. The schedule definition itself is never modified either way, and runs triggered over MCP now carry a reason (MCP: Trigger Bolt run or MCP: Trigger Bolt run with overrides) so you can tell them apart in Bolt. The same split applies to DinoAI agents. An agent whose tools.list allowlists trigger_bolt_schedule_run and passes commands to it now gets an explicit refusal pointing at the other tool, so add trigger_bolt_schedule_run_with_overrides to the allowlist if your agent overrides commands or a branch. Shipped in Paradime v6.12.0.