run_conversation_analysis
A execute tool on the Elevenlabs MCP server.
This record as markdown: /tools/aiwerk-mcp-server-elevenlabs/run-conversation-analysis.md
What run_conversation_analysis does on Elevenlabs
AI agents invoke run_conversation_analysis to trigger actions in Elevenlabs. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
| Parameter | Type | Required | Description |
|---|---|---|---|
conversation_id | string | Yes | ID of the conversation |
Parameters from the server's own tool schema.
Why run_conversation_analysis is rated High
run_conversation_analysis triggers real processes with real consequences. An agent gone sideways doesn't fire it once. It starts dozens of builds, sends mass notifications, or burns through compute before anyone looks up.
Attacks that exploit this kind of access
The rule that runs run_conversation_analysis safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Elevenlabs, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For run_conversation_analysis, this is the rule to start with:
run_conversation_analysis stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Elevenlabs, apply this rule, and every run_conversation_analysis call is checked against it from then on.
Questions about run_conversation_analysis
run_conversation_analysis is a execute tool on the Elevenlabs MCP server. It is categorised as a Execute tool in the Elevenlabs MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
run_conversation_analysis accepts 1 parameter: conversation_id. Required: conversation_id. The full parameter table on this page comes from the server's own tool schema.
Register the Elevenlabs MCP server in PolicyLayer and add a rule for run_conversation_analysis: 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 Elevenlabs. Nothing to install.
run_conversation_analysis is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the run_conversation_analysis 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 run_conversation_analysis. 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.
run_conversation_analysis is provided by the Elevenlabs MCP server (@aiwerk/mcp-server-elevenlabs). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Elevenlabs, and thousands of servers like it.
Across the catalogue