rank_hook_candidates
List and rank all hook candidates in the session.
This record as markdown: /tools/io-github-dreamrec-livepilot/rank-hook-candidates.md
What rank_hook_candidates does on Livepilot
AI agents call rank_hook_candidates 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 rank_hook_candidates is rated Low
This tool queries and analyzes existing musical content (hook candidates) to provide ranked results. It performs no writes, deletions, or external operations. The 'medium' severity reflects that an AI agent could misuse ranking logic to suggest unsuitable hooks or make poor creative decisions, but this does not alter session state or cause irreversible harm.
From the tool's definition Tool description states 'List and rank all hook candidates in the session' — a pure retrieval and analysis operation with no modification or side effects.
Attacks that exploit this kind of access
The rule that runs rank_hook_candidates 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 rank_hook_candidates, this is the rule to start with:
rank_hook_candidates 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 rank_hook_candidates call is checked against it from then on.
Questions about rank_hook_candidates
List and rank all hook candidates in the 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 rank_hook_candidates: 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.
rank_hook_candidates 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 rank_hook_candidates 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 rank_hook_candidates. 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.
rank_hook_candidates 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