Get available input routing options for a track.
AI agents call get_available_inputs to retrieve information from Ableton without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries configuration or state information about track inputs in Ableton Live. It has no side effects, does not create, modify, or delete data, and does not execute commands or move resources. It is a straightforward read/retrieval operation, making it the lowest risk category with minimal blast radius if misused by an AI agent.
From the tool's definition Tool name and description indicate it retrieves information about available input routing options without modifying state: 'Get available input routing options for a track.' The verb 'get' and read-only nature confirm this is a query operation.
Documented attack patterns abuse exactly the kind of access get_available_inputs gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Ableton, and nothing reaches the server without passing your rules. This is the rule we recommend for get_available_inputs:
{
"version": "1",
"default": "deny",
"tools": {
"get_available_inputs": {}
}
}get_available_inputs is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get available input routing options for a track. It is categorised as a Read tool in the Ableton MCP Server, which means it retrieves data without modifying state.
Register the Ableton MCP server in PolicyLayer and add a rule for get_available_inputs: 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 Ableton. Nothing to install.
get_available_inputs 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_available_inputs 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_available_inputs. 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_available_inputs is provided by the Ableton MCP server (jpoindexter/ableton-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Ableton, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
128 Ableton tools catalogued and risk-classified — across an index of 43,000+ MCP servers.