corpus_remove_source

Remove a source from the manifest.

SERVERLivepilot SOURCElivepilot

Critical RISK CLASS

Category Destructive

Parameters 00 required

Recommended Hiddensee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-dreamrec-livepilot/corpus-remove-source.md

WHAT IT DOES

What corpus_remove_source does on Livepilot

AI agents call corpus_remove_source 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.

RISK

Why corpus_remove_source is rated Critical

This tool deletes a source from the manifest, which is an irreversible operation that cannot be undone through the tool's normal interface. In a music production context, removing a source from a manifest could result in loss of audio data, sample references, or project configuration that was stored there.

From the tool's definition Tool name contains 'remove' and description states 'Remove a source from the manifest.' The verb 'remove' in the context of manifest management indicates irreversible deletion of a data source.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs corpus_remove_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_remove_source, this is the rule to start with:

corpus_remove_source Hidden

corpus_remove_source is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "corpus_remove_source"
  ]
}

RESTRICT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Livepilot, apply this rule, and every corpus_remove_source call is checked against it from then on.

FAQ

Questions about corpus_remove_source

What does the corpus_remove_source tool do? +

Remove a source from the manifest. 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.

How do I enforce a policy on corpus_remove_source? +

Register the Livepilot MCP server in PolicyLayer and add a rule for corpus_remove_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.

What risk level is corpus_remove_source? +

corpus_remove_source is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit corpus_remove_source? +

Yes. Add a rate_limit block to the corpus_remove_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.

How do I block corpus_remove_source completely? +

Set action: deny in the PolicyLayer policy for corpus_remove_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.

What MCP server provides corpus_remove_source? +

corpus_remove_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.

KEEP EXPLORING

More on Livepilot, and thousands of servers like it.

This server

All 474 Livepilot tools → Critical-risk tools on this server →

Across the catalogue

remove_video on Mcptube Vision →remove_2fa on cPanel MCP Server →remove_concept on MegaMemory →task_assignees_remove on Vikunja → All critical-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Blast radius →Tool call approval →