This record as markdown: /tools/io-github-dreamrec-livepilot/corpus-add-source.md
What corpus_add_source does on Livepilot
AI agents use corpus_add_source 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 corpus_add_source is rated Medium
The tool appears to add/create a new source within a corpus structure, which is a reversible modification operation. Without a description, confidence is reduced, but the naming pattern and sibling tools (add_arrangement_notes, add_drum_rack_pad, add_notes, add_rack_macro) all follow write semantics.
From the tool's definition Tool name 'corpus_add_source' suggests adding a source to a corpus (collection). The 'add_' prefix and context of an Ableton Live music production copilot indicate a write operation that creates or modifies data.
Attacks that exploit this kind of access
The rule that runs corpus_add_source 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 corpus_add_source, this is the rule to start with:
corpus_add_source 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 corpus_add_source call is checked against it from then on.
Questions about corpus_add_source
corpus_add_source 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 corpus_add_source: 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.
corpus_add_source 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 corpus_add_source 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 corpus_add_source. 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.
corpus_add_source 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