This record as markdown: /tools/io-github-dreamrec-livepilot/compose-full-apply.md
What compose_full_apply does on Livepilot
AI agents use compose_full_apply to create or update resources in Livepilot, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Livepilot environment.
Why compose_full_apply is rated Medium
Based on the tool name, 'compose_full_apply' likely creates or applies a full composition to the project, which would be a Write operation. However, with no description available, confidence is low. Given the context of an Ableton Live MCP server focused on music production, this tool likely writes/applies compositional data to the session. Severity is medium as misuse could overwrite existing composition work.
From the tool's definition Tool name 'compose_full_apply' suggests composing and applying changes; description is empty and uninformative.
Attacks that exploit this kind of access
The rule that runs compose_full_apply 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 compose_full_apply, this is the rule to start with:
compose_full_apply stays usable, but capped: an agent stuck in a loop can't make hundreds of changes 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 compose_full_apply call is checked against it from then on.
Questions about compose_full_apply
compose_full_apply is a write tool on the Livepilot MCP server. It is categorised as a Write tool in the Livepilot MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Livepilot MCP server in PolicyLayer and add a rule for compose_full_apply: 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.
compose_full_apply is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the compose_full_apply 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 compose_full_apply. 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.
compose_full_apply 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.
This server
Across the catalogue