get_hidden_parameters

What get_hidden_parameters does on Livepilot

AI agents call get_hidden_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_hidden_parameters is rated Low

The tool appears to retrieve hidden parameters from Ableton Live's internal state—likely querying existing configuration or metadata. No description was provided, which reduces confidence slightly. However, the 'get_' naming convention strongly suggests read-only retrieval with no side effects. Even if parameters are 'hidden,' accessing them poses minimal risk compared to modifying them.

From the tool's definition Tool name 'get_hidden_parameters' indicates retrieval of parameter data without modification. The 'get_' prefix and lack of any write/execute/delete verbs suggest a read-only query operation.

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

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

Questions about get_hidden_parameters