This record as markdown: /tools/io-github-dreamrec-livepilot/get-scenes-info.md
What get_scenes_info does on Livepilot
AI agents call get_scenes_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_scenes_info is rated Low
This tool queries and retrieves metadata about Ableton Live scenes without creating, modifying, deleting, or executing any operations. It has no side effects on the project state. The information retrieved (scene names, tempos, colors) is non-sensitive metadata within a music production context with minimal blast radius if misused.
From the tool's definition Tool is named 'get_scenes_info' and described as 'Get info for all scenes: name, tempo, color.' The verb 'get' and the read-only nature of retrieving scene metadata (name, tempo, color) with no modification capability indicates pure data retrieval.
Attacks that exploit this kind of access
The rule that runs get_scenes_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_scenes_info, this is the rule to start with:
get_scenes_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_scenes_info call is checked against it from then on.
Questions about get_scenes_info
Get info for all scenes: name, tempo, color. 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_scenes_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_scenes_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_scenes_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_scenes_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_scenes_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