rank_moves_by_taste
Rank semantic moves by taste fit for the current user.
This record as markdown: /tools/io-github-dreamrec-livepilot/rank-moves-by-taste.md
What rank_moves_by_taste does on Livepilot
AI agents call rank_moves_by_taste 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_moves_by_taste is rated Low
This tool retrieves and ranks existing data (semantic moves) according to user taste preferences, returning a scored list. It is a pure read operation with no side effects on the Ableton Live project or external systems. The sibling tools (add_*, analyze_*) confirm this server's domain is music production; 'rank_*' is a query/analysis function typical of recommendation systems.
From the tool's definition Tool name is 'rank_moves_by_taste' and description states it 'Rank[s] semantic moves by taste fit' — a ranking/scoring operation. No modification of user data, no execution of code, no destructive actions, and no financial operations.
Attacks that exploit this kind of access
The rule that runs rank_moves_by_taste 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_moves_by_taste, this is the rule to start with:
rank_moves_by_taste 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_moves_by_taste call is checked against it from then on.
Questions about rank_moves_by_taste
Rank semantic moves by taste fit for the current user. 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_moves_by_taste: 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_moves_by_taste 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_moves_by_taste 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_moves_by_taste. 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_moves_by_taste 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