Skip to main content
September 9, 2026 The Paradime MCP server let any role that can trigger a Bolt schedule also override the commands and branch that run used. In the app that is not true: overriding a run is an admin-level action. This release closes that gap by splitting the tool in two. 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. The schedule definition itself is never modified either way, and runs triggered over MCP now carry a reason (MCP: Trigger Bolt run or MCP: Modify and trigger Bolt run) 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 modify_and_trigger_bolt_schedule_run to the allowlist if your agent overrides commands or a branch. Shipped in Paradime v6.12.0.