corpus_detect_plugins

A read tool on the Livepilot MCP server.

SERVERLivepilot SOURCElivepilot

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-dreamrec-livepilot/corpus-detect-plugins.md

WHAT IT DOES

What corpus_detect_plugins does on Livepilot

AI agents call corpus_detect_plugins to retrieve information from Livepilot without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why corpus_detect_plugins is rated Low

The name implies scanning or querying plugin state ('detect') rather than modifying, executing commands, or deleting data. In the context of an Ableton Live copilot, this likely reads plugin information from the session. However, confidence is moderate because the description is empty and the exact behavior cannot be fully determined.

From the tool's definition Tool name 'corpus_detect_plugins' suggests detection/identification of plugins; no description provided to clarify intent.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

corpus_detect_plugins Allowed

corpus_detect_plugins is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "corpus_detect_plugins": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about corpus_detect_plugins

What does the corpus_detect_plugins tool do? +

corpus_detect_plugins is a read tool on the Livepilot MCP server. It is categorised as a Read tool in the Livepilot MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on corpus_detect_plugins? +

Register the Livepilot MCP server in PolicyLayer and add a rule for corpus_detect_plugins: 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_detect_plugins? +

corpus_detect_plugins is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit corpus_detect_plugins? +

Yes. Add a rate_limit block to the corpus_detect_plugins 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_detect_plugins completely? +

Set action: deny in the PolicyLayer policy for corpus_detect_plugins. 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_detect_plugins? +

corpus_detect_plugins 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 →

Across the catalogue

detect_slop on Slop Cop → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →