macros_trigger

What macros_trigger does on Propresenter

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

This tool runs a macro in ProPresenter 7, executing predetermined sequences of commands. While the blast radius depends on what the macro does, triggering arbitrary macros in a presentation system can cause unintended presentation changes, audio playback, or other side effects. This qualifies as Execute rather than Write because it activates programmatic operations rather than creating/modifying data directly.

From the tool's definition Tool name is 'macros_trigger' and description states 'Trigger a specific macro'. The verb 'trigger' indicates execution of a macro, which is an external operation whose effects depend on arguments (which macro is specified).

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

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

Questions about macros_trigger