bitrix24_start_workflow

What bitrix24_start_workflow does on Allmcp

AI agents invoke bitrix24_start_workflow to trigger actions in Allmcp. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.

Why bitrix24_start_workflow is rated High

Starting a workflow executes external operations whose effects depend on what the workflow performs—potentially creating records, sending notifications, triggering approvals, or executing business logic. This is not a simple read (no retrieval pattern), not destructive (workflows typically don't irreversibly delete), and not financial (unless the workflow itself handles payments).

From the tool's definition Tool name 'bitrix24_start_workflow' indicates triggering/execution of a workflow process. Description is empty, limiting direct confirmation, but the verb 'start' combined with 'workflow' in a business integration context (Bitrix24 is an enterprise…

The rule that runs bitrix24_start_workflow safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Allmcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For bitrix24_start_workflow, this is the rule to start with:

{
  "version": "1",
  "default": "deny",
  "tools": {
    "bitrix24_start_workflow": {
      "limits": [
        {
          "counter": "bitrix24_start_workflow_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

Questions about bitrix24_start_workflow