announcement_trigger_next

// WHEN AI AGENTS USE THIS TOOL

AI agents invoke announcement_trigger_next to trigger processes or run actions in Propresenter. Execute operations can have side effects beyond the immediate call -- triggering builds, sending notifications, or starting workflows. Rate limits and argument validation are essential to prevent runaway execution.

// WHY ENFORCE A POLICY ON ANNOUNCEMENT_TRIGGER_NEXT

announcement_trigger_next can trigger processes with real-world consequences. An uncontrolled agent might start dozens of builds, send mass notifications, or kick off expensive compute jobs. Intercept enforces rate limits and validates arguments to keep execution within safe bounds.

// RECOMMENDED POLICY

Execute tools trigger processes. Rate-limit and validate arguments to prevent unintended side effects.

io-github-alxpark-propresenter-mcp.yaml

tools:
  announcement_trigger_next:
    rules:
      - action: allow
        rate_limit:
          max: 10
          window: 60
        validate:
          required_args: true

See the full Propresenter policy for all 177 tools.

// DETAILS

Tool Name announcement_trigger_next

Category Execute

MCP Server Propresenter MCP Server

Risk Level High

// MORE PROPRESENTER TOOLS

Destructive clear_get_group Destructive clear_get_groups Destructive clear_layer Destructive clear_trigger_group Destructive messages_clear Destructive messages_delete Destructive props_clear Destructive props_delete

View all 177 tools →

// RELATED READING

// FAQ

What does the announcement_trigger_next tool do? +

Trigger the next cue in the active announcement. 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 announcement_trigger_next? +

Add a rule in your Intercept YAML policy under the tools section for announcement_trigger_next. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Propresenter MCP server.

What risk level is announcement_trigger_next? +

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

Can I rate-limit announcement_trigger_next? +

Yes. Add a rate_limit block to the announcement_trigger_next rule in your Intercept 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 announcement_trigger_next completely? +

Set action: deny in the Intercept policy for announcement_trigger_next. 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 announcement_trigger_next? +

announcement_trigger_next is provided by the Propresenter MCP server (@alxpark/propresenter-mcp). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policies on Propresenter