measure_hook_salience
Measure the salience of a specific hook or the primary hook.
This record as markdown: /tools/io-github-dreamrec-livepilot/measure-hook-salience.md
What measure_hook_salience does on Livepilot
AI agents call measure_hook_salience 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 measure_hook_salience is rated Low
This tool queries or analyzes properties of existing musical content (hook salience analysis) within Ableton Live without creating, modifying, deleting, or executing arbitrary operations. It is a read-only analytical function typical of music production copilots that examine composition properties. The low severity reflects that misuse would only affect local analysis results, not data integrity or external systems.
From the tool's definition The tool 'measure_hook_salience' is described as measuring salience of a hook—a purely analytical/observational operation.
Attacks that exploit this kind of access
The rule that runs measure_hook_salience 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 measure_hook_salience, this is the rule to start with:
measure_hook_salience 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 measure_hook_salience call is checked against it from then on.
Questions about measure_hook_salience
Measure the salience of a specific hook or the primary hook. 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 measure_hook_salience: 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.
measure_hook_salience 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 measure_hook_salience 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 measure_hook_salience. 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.
measure_hook_salience 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