transport_skip_backward
Skip backward in the specified layer by a given time
This record as markdown: /tools/io-github-alxpark-propresenter-mcp/transport-skip-backward.md
What transport_skip_backward does on Propresenter
AI agents invoke transport_skip_backward 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_skip_backward is rated High
This tool controls media transport playback by skipping backward in time on a specified layer within ProPresenter 7. It executes an external operation that changes the playback state of a live presentation system. It does not read data, write/create content, delete anything, or involve finances — it triggers a real-time playback control action.
From the tool's definition 'Skip backward in the specified layer by a given time' — triggers a transport/playback operation on an external system (ProPresenter 7)
Attacks that exploit this kind of access
The rule that runs transport_skip_backward 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_skip_backward, this is the rule to start with:
transport_skip_backward 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_skip_backward call is checked against it from then on.
Questions about transport_skip_backward
Skip backward in the specified layer by a given time. 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_skip_backward: 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_skip_backward 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_skip_backward 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_skip_backward. 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_skip_backward 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