High Risk

trigger_presentation_cue

Trigger a specific cue by index in a presentation by UUID

Single-target operation

Part of the Propresenter MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.

@alxpark/propresenter-mcp Execute Risk 3/5

AI agents invoke trigger_presentation_cue 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.

trigger_presentation_cue 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.

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

io-github-alxpark-propresenter-mcp.yaml
tools:
  trigger_presentation_cue:
    rules:
      - action: allow
        rate_limit:
          max: 10
          window: 60
        validate:
          required_args: true

See the full Propresenter policy for all 177 tools.

Tool Name trigger_presentation_cue
Category Execute
Risk Level High

View all 177 tools →

What does the trigger_presentation_cue tool do? +

Trigger a specific cue by index in a presentation by UUID. 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 trigger_presentation_cue? +

Add a rule in your Intercept YAML policy under the tools section for trigger_presentation_cue. 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 trigger_presentation_cue? +

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

Can I rate-limit trigger_presentation_cue? +

Yes. Add a rate_limit block to the trigger_presentation_cue 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 trigger_presentation_cue completely? +

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

trigger_presentation_cue 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

Open source. One binary. Zero dependencies.

npx -y @policylayer/intercept
github.com/policylayer/intercept →
// GET IN TOUCH

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

Message sent.

We'll get back to you soon.