プロジェクトの構成表を生成（シーン×トラックのクリップ配置、小節数、テンポ）
AI agents call get_project_table to retrieve information from Ableton MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and displays information about the current Ableton project structure (scenes, tracks, clips, measures, tempo) for visualization/analysis purposes. It performs no creation, modification, deletion, or external execution. The operation is read-only and informational, making it a Read category tool with low risk severity.
From the tool's definition Tool name 'get_project_table' and description indicate it 'generates a project structure table (clip placement in scenes × tracks, measure count, tempo)' — a retrieval and query operation that reads project metadata without modification or side effects.
Attacks that exploit this kind of access
プロジェクトの構成表を生成（シーン×トラックのクリップ配置、小節数、テンポ）. It is categorised as a Read tool in the Ableton MCP MCP Server, which means it retrieves data without modifying state.
Register the Ableton MCP server in PolicyLayer and add a rule for get_project_table: 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 MCP. Nothing to install.
get_project_table 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_project_table 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_project_table. 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_project_table is provided by the Ableton MCP server (keigotak/abletonmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →