find_primary_hook
Find the most salient hook in the current session.
This record as markdown: /tools/io-github-dreamrec-livepilot/find-primary-hook.md
What find_primary_hook does on Livepilot
AI agents call find_primary_hook 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 find_primary_hook is rated Low
This tool performs a read-only query of the current Ableton Live session to identify a musical hook. It retrieves and analyzes data but does not create, modify, delete, or execute any operations that change the session state. The only potential blast radius is if the analysis result is used to inform subsequent actions, but the tool itself is purely informational.
From the tool's definition The tool 'find_primary_hook' is described as finding 'the most salient hook in the current session' — a retrieval and analysis operation with no modification, deletion, or external side effects.
Attacks that exploit this kind of access
The rule that runs find_primary_hook 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 find_primary_hook, this is the rule to start with:
find_primary_hook 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 find_primary_hook call is checked against it from then on.
Questions about find_primary_hook
Find the most salient hook in the current session. 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 find_primary_hook: 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.
find_primary_hook 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 find_primary_hook 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 find_primary_hook. 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.
find_primary_hook 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