bitrix24_clock_in

What bitrix24_clock_in does on Allmcp

AI agents invoke bitrix24_clock_in 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_clock_in is rated High

This tool executes a specific action in an external system (Bitrix24 time tracking) rather than simply reading or writing data. Clock-in operations modify system state and trigger side effects in a time-tracking workflow. While not destructive or financial, it represents a command execution that could be misused to falsify work records if an AI agent invokes it maliciously or without proper authorization.

From the tool's definition Tool name is 'bitrix24_clock_in' and description states 'Clock in (start work day) in Bitrix24 time tracking.' The action triggers an external operation (time tracking system state change) whose effects depend on context (which user, which timestamp).

The rule that runs bitrix24_clock_in 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_clock_in, this is the rule to start with:

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

Questions about bitrix24_clock_in