get_scene_matrix
Get the full session clip grid: every track x every scene.
This record as markdown: /tools/io-github-dreamrec-livepilot/get-scene-matrix.md
What get_scene_matrix does on Livepilot
AI agents call get_scene_matrix 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_scene_matrix is rated Low
This tool queries and returns the structure of Ableton Live's session view (tracks and scenes) without modifying, executing, or deleting anything. It is a straightforward data retrieval operation with no side effects. Severity is low because the information returned is configuration/structural metadata of the user's own project, posing minimal risk even if retrieved inappropriately.
From the tool's definition Tool name 'get_scene_matrix' and description 'Get the full session clip grid: every track x every scene' indicate data retrieval with no modification. The verb 'Get' and lack of any write/execute/delete language confirm read-only behavior.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs get_scene_matrix 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_scene_matrix, this is the rule to start with:
get_scene_matrix 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_scene_matrix call is checked against it from then on.
Questions about get_scene_matrix
Get the full session clip grid: every track x every scene. 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_scene_matrix: 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_scene_matrix 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_scene_matrix 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_scene_matrix. 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_scene_matrix 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