High Risk →

transport_go_to_end

Go to the end of content in the specified layer

How to control transport_go_to_end ↓

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.

High Risk

Why transport_go_to_end needs a policy

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

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

How to control transport_go_to_end

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

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

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.

  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 transport_go_to_end

What does the transport_go_to_end tool do? +

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.

How do I enforce a policy on transport_go_to_end? +

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.

What risk level is transport_go_to_end? +

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

Can I rate-limit transport_go_to_end? +

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.

How do I block transport_go_to_end completely? +

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.

What MCP server provides transport_go_to_end? +

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.

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.