discard_wonder_session
Reject all Wonder variants and close the session.
This record as markdown: /tools/io-github-dreamrec-livepilot/discard-wonder-session.md
What discard_wonder_session does on Livepilot
AI agents call discard_wonder_session to permanently remove resources in Livepilot, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why discard_wonder_session is rated Critical
This tool performs an irreversible action—closing and discarding a session without apparent confirmation or recovery mechanism. In the context of music production (Ableton Live), closing a session without saving discards all work. This cannot be undone programmatically and represents data loss, placing it in the Destructive category rather than merely Execute.
From the tool's definition Tool name 'discard_wonder_session' combined with description 'Reject all Wonder variants and close the session' indicates irreversible closure and discarding of session data.
Attacks that exploit this kind of access
The rule that runs discard_wonder_session 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 discard_wonder_session, this is the rule to start with:
discard_wonder_session is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Livepilot, apply this rule, and every discard_wonder_session call is checked against it from then on.
Questions about discard_wonder_session
Reject all Wonder variants and close the session. It is categorised as a Destructive tool in the Livepilot MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Livepilot MCP server in PolicyLayer and add a rule for discard_wonder_session: 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.
discard_wonder_session is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the discard_wonder_session 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 discard_wonder_session. 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.
discard_wonder_session 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