timers_start

What timers_start does on Propresenter

AI agents invoke timers_start to trigger actions in Propresenter. 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 timers_start is rated High

The tool executes a command that initiates a timer in an external application, which is an operational side effect. It is not a simple read operation (no data retrieval), nor is it destructive or financial. It falls under Execute because it triggers an external operation whose actual impact depends on the arguments provided (which specific timer, and what that timer controls in the presentation context).

From the tool's definition Tool name 'timers_start' and description 'Start a specific timer' indicate this triggers an external operation (timer activation) on ProPresenter 7, which is an audio/visual presentation software.

The rule that runs timers_start safely

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

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

Questions about timers_start