search_voices
AI agents call search_voices to retrieve information from Ableton MCP Extended without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool appears to retrieve or query available voices from the ElevenLabs integration, with no side effects. It follows the Read category pattern of search/query operations that retrieve data without modification. Severity is low due to minimal blast radius—miscalling this tool would only return unwanted voice options, not cause harm.
From the tool's definition Tool is named 'search_voices' within the Ableton MCP Extended server context that integrates ElevenLabs for AI-generated audio. The 'search' verb and lack of action qualifiers (add, delete, modify, fire) indicate a query/retrieval operation.
Attacks that exploit this kind of access
search_voices. It is categorised as a Read tool in the Ableton MCP Extended MCP Server, which means it retrieves data without modifying state.
Register the Ableton MCP Extended MCP server in PolicyLayer and add a rule for search_voices: 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 Extended. Nothing to install.
search_voices 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 search_voices 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 search_voices. 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.
search_voices is provided by the Ableton MCP Extended MCP server (kevinzhang03/ableton-mcp). 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 →