This record as markdown: /tools/io-github-dreamrec-livepilot/render-preview-variant.md
What render_preview_variant does on Livepilot
AI agents invoke render_preview_variant to trigger actions in Livepilot. 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 render_preview_variant is rated High
The name implies executing a render operation (generating audio/media output), which is an external operation with effects that depend on arguments. With no description available, confidence is low, but 'render' typically involves executing a process rather than a simple read or write. Severity is medium as misuse could trigger unintended rendering operations in Ableton Live.
From the tool's definition Tool name 'render_preview_variant' suggests rendering/executing a preview generation process; description is empty and uninformative.
Attacks that exploit this kind of access
The rule that runs render_preview_variant safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Livepilot, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For render_preview_variant, this is the rule to start with:
render_preview_variant 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 Livepilot, apply this rule, and every render_preview_variant call is checked against it from then on.
Questions about render_preview_variant
render_preview_variant is a execute tool on the Livepilot MCP server. It is categorised as a Execute tool in the Livepilot MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Livepilot MCP server in PolicyLayer and add a rule for render_preview_variant: 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 Livepilot. Nothing to install.
render_preview_variant 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 render_preview_variant 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 render_preview_variant. 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.
render_preview_variant is provided by the Livepilot MCP server (livepilot). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Livepilot, and thousands of servers like it.
Across the catalogue