transport_go_to_end
Go to the end of content in the specified layer
This record as markdown: /tools/io-github-alxpark-propresenter-mcp/transport-go-to-end.md
What transport_go_to_end does on Propresenter
AI agents invoke transport_go_to_end 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_go_to_end is rated High
This tool triggers a transport/playback operation in ProPresenter 7 — jumping to the end of content in a layer. It causes an external system state change (presentation control), making it Execute. Misuse could disrupt a live presentation but doesn't destroy or create data.
From the tool's definition Go to the end of content in the specified layer
Attacks that exploit this kind of access
The rule that runs transport_go_to_end 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_go_to_end, this is the rule to start with:
transport_go_to_end 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_go_to_end call is checked against it from then on.
Questions about transport_go_to_end
Go to the end of content in the specified 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_go_to_end: 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_go_to_end 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_go_to_end 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_go_to_end. 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_go_to_end 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