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.
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).
Documented attack patterns abuse exactly the kind of access macros_trigger gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Propresenter, and nothing reaches the server without passing your rules. This is the rule we recommend for macros_trigger:
{
"version": "1",
"default": "deny",
"tools": {
"macros_trigger": {
"limits": [
{
"counter": "macros_trigger_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}macros_trigger stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Trigger a specific macro. It is categorised as a Execute tool in the Propresenter MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Propresenter MCP server in PolicyLayer and add a rule for macros_trigger: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches Propresenter. Nothing to install.
macros_trigger is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the macros_trigger rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.
Set action: deny in the PolicyLayer policy for macros_trigger. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.
macros_trigger is provided by the Propresenter MCP server (@alxpark/propresenter-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Propresenter, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
177 Propresenter tools catalogued and risk-classified — across an index of 43,000+ MCP servers.