High Risk →

clear_trigger_group

Trigger a specific clear group

How to control clear_trigger_group ↓

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.

High Risk

Why clear_trigger_group needs a policy

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

Documented attack patterns abuse exactly the kind of access clear_trigger_group gives an agent:

How to control clear_trigger_group

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 clear_trigger_group:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "clear_trigger_group": {
      "limits": [
        {
          "counter": "clear_trigger_group_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

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.

  1. Create a free account and register Propresenter — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
RATE-LIMIT THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about clear_trigger_group

What does the clear_trigger_group tool do? +

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.

How do I enforce a policy on clear_trigger_group? +

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.

What risk level is clear_trigger_group? +

clear_trigger_group is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit clear_trigger_group? +

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.

How do I block clear_trigger_group completely? +

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.

What MCP server provides clear_trigger_group? +

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.

Enforce policy on every Propresenter tool call.

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.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.