clear_trigger_group
Trigger a specific clear group
This record as markdown: /tools/io-github-alxpark-propresenter-mcp/clear-trigger-group.md
What clear_trigger_group does on Propresenter
AI agents invoke clear_trigger_group 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 clear_trigger_group is rated High
The tool 'triggers' a clear group in ProPresenter, which executes an action (clearing/triggering a group) in an external presentation application. This is an Execute-level operation as it causes an external effect dependent on arguments, though 'clear' could imply some content removal which might be partially destructive.
From the tool's definition Trigger a specific clear group
Attacks that exploit this kind of access
The rule that runs clear_trigger_group 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 clear_trigger_group, this is the rule to start with:
clear_trigger_group 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Propresenter, apply this rule, and every clear_trigger_group call is checked against it from then on.
Questions about clear_trigger_group
Trigger a specific clear group. 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 clear_trigger_group: 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.
clear_trigger_group 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 clear_trigger_group 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 clear_trigger_group. 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.
clear_trigger_group 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.
More on Propresenter, and thousands of servers like it.
Across the catalogue