This record as markdown: /tools/io-github-dreamrec-livepilot/create-experiment.md
What create_experiment does on Livepilot
AI agents use create_experiment 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 create_experiment is rated Medium
The tool most likely creates or adds a new experiment record within the Ableton Live project, similar to other 'add_*' operations on this server. This is reversible data creation (Write category) rather than destruction or code execution. Confidence is moderate (0.65) because the empty description prevents full certainty, but the naming pattern and server context strongly suggest a Write operation.
From the tool's definition Tool name 'create_experiment' combined with context of an Ableton Live 12 music production server suggests creating a new experiment object or session state.
Attacks that exploit this kind of access
The rule that runs create_experiment 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 create_experiment, this is the rule to start with:
create_experiment 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 create_experiment call is checked against it from then on.
Questions about create_experiment
create_experiment 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 create_experiment: 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.
create_experiment 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 create_experiment 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 create_experiment. 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.
create_experiment 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