> ## Documentation Index
> Fetch the complete documentation index at: https://docs.paradime.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Overriding a Bolt run over MCP now needs its own permission

> The MCP Bolt trigger is split in two: running a schedule as configured, and overriding its commands or branch, now a separate workspace permission.

*September 9, 2026*

The Paradime [MCP server](/products/dino-ai/mcp-server/index) 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.

| Tool                                   | What it does                                                          | Who can use it                                                                       |
| -------------------------------------- | --------------------------------------------------------------------- | ------------------------------------------------------------------------------------ |
| `trigger_bolt_schedule_run`            | Runs a schedule exactly as configured                                 | Anyone who can trigger schedules, including Analysts                                 |
| `modify_and_trigger_bolt_schedule_run` | Runs a schedule with overridden commands or branch, for that run only | Roles that can also create schedules: Admin, Workspace admin, Developer, and Sandbox |

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`](/products/dino-ai/programmable-agents/tools-reference) to the allowlist if your agent overrides commands or a branch.

Shipped in Paradime v6.12.0.


## Related topics

- [DinoAI can now read and update HubSpot](/changelog/2026-09-03/hubspot-tools.md)
- [Paradime MCP server: connect AI clients to your data](/products/dino-ai/mcp-server/index.md)
- [Connect MCP clients to Paradime with OAuth](/changelog/2026-08-26/mcp-oauth.md)
- [Bring Your Own Cloud on GCP](/products/settings/deployment/byoc/gcp.md)
- [Environment Variable Overrides](/products/bolt/creating-schedules/schedules-environment-variables.md)