run_conversation_simulation_route_stream

Simulates A Conversation (Stream) Deprecated upstream.

SERVERElevenlabs SOURCE@aiwerk/mcp-server-elevenlabs

High RISK CLASS

Category Execute

Parameters 42 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/aiwerk-mcp-server-elevenlabs/run-conversation-simulation-route-stream.md

WHAT IT DOES

What run_conversation_simulation_route_stream does on Elevenlabs

AI agents invoke run_conversation_simulation_route_stream 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
`agent_id`	string	Yes	The id of an agent. This is returned on agent creation.
`new_turns_limit`	number	—	Maximum number of new turns to generate in the conversation simulation
`simulation_specification`	object	Yes	A specification that will be used to simulate a conversation between an agent and an AI user.
`extra_evaluation_criteria`	object	—

Parameters from the server's own tool schema.

RISK

Why run_conversation_simulation_route_stream is rated High

run_conversation_simulation_route_stream 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

RECOMMENDED RULE

The rule that runs run_conversation_simulation_route_stream 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_simulation_route_stream, this is the rule to start with:

run_conversation_simulation_route_stream Rate-limited

run_conversation_simulation_route_stream 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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "run_conversation_simulation_route_stream": {
      "limits": [
        {
          "counter": "run_conversation_simulation_route_stream_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Elevenlabs, apply this rule, and every run_conversation_simulation_route_stream call is checked against it from then on.

FAQ

Questions about run_conversation_simulation_route_stream

What does the run_conversation_simulation_route_stream tool do? +

Simulates A Conversation (Stream) Deprecated upstream. 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.

What parameters does run_conversation_simulation_route_stream accept? +

run_conversation_simulation_route_stream accepts 4 parameters: agent_id, new_turns_limit, simulation_specification, extra_evaluation_criteria. Required: agent_id, simulation_specification. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on run_conversation_simulation_route_stream? +

Register the Elevenlabs MCP server in PolicyLayer and add a rule for run_conversation_simulation_route_stream: 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.

What risk level is run_conversation_simulation_route_stream? +

run_conversation_simulation_route_stream is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit run_conversation_simulation_route_stream? +

Yes. Add a rate_limit block to the run_conversation_simulation_route_stream 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.

How do I block run_conversation_simulation_route_stream completely? +

Set action: deny in the PolicyLayer policy for run_conversation_simulation_route_stream. 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.

What MCP server provides run_conversation_simulation_route_stream? +

run_conversation_simulation_route_stream 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.

KEEP EXPLORING

More on Elevenlabs, and thousands of servers like it.

This server

All 390 Elevenlabs tools → High-risk tools on this server →

Across the catalogue

run on 0sec →shortcuts_run on Apple Apps MCP →run_emba_scan on EMBA-MCP → All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →