This record as markdown: /tools/io-github-dreamrec-livepilot/get-plugin-parameters.md
What get_plugin_parameters does on Livepilot
AI agents call get_plugin_parameters 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.
Why get_plugin_parameters is rated Low
The tool retrieves or queries plugin parameter settings within Ableton Live without creating, modifying, or executing actions. This is a non-invasive read operation with no side effects. Low severity because retrieving parameter values poses minimal risk—an AI agent querying plugin state cannot damage audio data or trigger unintended production changes.
From the tool's definition Tool name 'get_plugin_parameters' indicates retrieval of plugin parameter data with no modification capability. The 'get_' prefix is a standard convention for read-only queries. Description is empty, reducing confidence slightly.
Attacks that exploit this kind of access
The rule that runs get_plugin_parameters 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 get_plugin_parameters, this is the rule to start with:
get_plugin_parameters is read-only, so it stays allowed. 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 get_plugin_parameters call is checked against it from then on.
Questions about get_plugin_parameters
get_plugin_parameters 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.
Register the Livepilot MCP server in PolicyLayer and add a rule for get_plugin_parameters: 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.
get_plugin_parameters is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_plugin_parameters 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 get_plugin_parameters. 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.
get_plugin_parameters 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