get_last_move
Return the most recent semantic move from the action ledger.
This record as markdown: /tools/io-github-dreamrec-livepilot/get-last-move.md
What get_last_move does on Livepilot
AI agents call get_last_move 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_last_move is rated Low
This tool reads from an action ledger to return the last recorded move. It performs data retrieval only, with no capability to modify, delete, or execute external operations. The blast radius of misuse is minimal—an AI agent could only obtain information about the most recent action taken in Ableton Live, which poses no risk to the music project itself.
From the tool's definition Tool name 'get_last_move' and description 'Return the most recent semantic move from the action ledger' indicate a query operation that retrieves historical data without modification or side effects.
Attacks that exploit this kind of access
The rule that runs get_last_move 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_last_move, this is the rule to start with:
get_last_move 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 get_last_move call is checked against it from then on.
Questions about get_last_move
Return the most recent semantic move from the action ledger. 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 get_last_move: 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.
get_last_move 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 get_last_move 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 get_last_move. 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.
get_last_move 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