transport_cancel_auto_advance
Cancel auto-advance for presentation or announcement layer
This record as markdown: /tools/io-github-alxpark-propresenter-mcp/transport-cancel-auto-advance.md
What transport_cancel_auto_advance does on Propresenter
AI agents invoke transport_cancel_auto_advance 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 transport_cancel_auto_advance is rated High
This tool triggers an operational action in ProPresenter — cancelling a scheduled auto-advance behavior. It modifies runtime state of the presentation software (stopping a timed progression), which is an external operation/trigger rather than a simple data read or write. It's reversible (auto-advance can be re-enabled), so not Destructive, but it does execute a command that affects live presentation flow.
From the tool's definition Cancel auto-advance for presentation or announcement layer
Attacks that exploit this kind of access
The rule that runs transport_cancel_auto_advance 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 transport_cancel_auto_advance, this is the rule to start with:
transport_cancel_auto_advance 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 transport_cancel_auto_advance call is checked against it from then on.
Questions about transport_cancel_auto_advance
Cancel auto-advance for presentation or announcement layer. 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 transport_cancel_auto_advance: 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.
transport_cancel_auto_advance 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 transport_cancel_auto_advance 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 transport_cancel_auto_advance. 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.
transport_cancel_auto_advance 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