get_session_info
Get comprehensive Ableton session state: tempo, tracks, scenes, transport.
This record as markdown: /tools/io-github-dreamrec-livepilot/get-session-info.md
What get_session_info does on Livepilot
AI agents call get_session_info 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_session_info is rated Low
This tool retrieves information about the current Ableton Live session (tempo, tracks, scenes, transport state) without modifying, deleting, or executing any operations. It is a pure query operation that returns data about the session state. No reversible or irreversible changes are made, no code is executed, and no external operations are triggered.
From the tool's definition Tool name is 'get_session_info' and description states 'Get comprehensive Ableton session state: tempo, tracks, scenes, transport.' The verb 'Get' and the action of retrieving session state indicate a read-only operation with no side effects.
Attacks that exploit this kind of access
The rule that runs get_session_info 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_session_info, this is the rule to start with:
get_session_info 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_session_info call is checked against it from then on.
Questions about get_session_info
Get comprehensive Ableton session state: tempo, tracks, scenes, transport. 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_session_info: 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_session_info 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_session_info 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_session_info. 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_session_info 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