get_conversation_users_route
Get Conversation Users.
This record as markdown: /tools/aiwerk-mcp-server-elevenlabs/get-conversation-users-route.md
What get_conversation_users_route does on Elevenlabs
AI agents call get_conversation_users_route to retrieve information from Elevenlabs without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
cursor | string | null | — | Used for fetching next page. Cursor is returned in the response. |
search | string | null | — | Search/filter by user ID (exact match). |
sort_by | string | — | The field to sort the results by. Defaults to last_contact_unix_secs. |
agent_id | string | null | — | Agent id (agent_…) or speech engine external id (seng_), resolved to the same underlying resource. |
branch_id | string | null | — | Filter conversations by branch ID. |
page_size | number | — | How many users to return at maximum. Defaults to 30. |
sort_direction | string | — | The direction to sort the results |
call_start_after_unix | number | null | — | Unix timestamp (in seconds) to filter conversations after to this start date. |
call_start_before_unix | number | null | — | Unix timestamp (in seconds) to filter conversations up to this start date. |
Parameters from the server's own tool schema.
Why get_conversation_users_route is rated Low
Even though get_conversation_users_route only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Attacks that exploit this kind of access
The rule that runs get_conversation_users_route 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 get_conversation_users_route, this is the rule to start with:
get_conversation_users_route is read-only, so it stays allowed. 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 get_conversation_users_route call is checked against it from then on.
Questions about get_conversation_users_route
Get Conversation Users. It is categorised as a Read tool in the Elevenlabs MCP Server, which means it retrieves data without modifying state.
get_conversation_users_route accepts 9 parameters: cursor, search, sort_by, agent_id, branch_id, page_size, sort_direction, call_start_after_unix, call_start_before_unix. 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 get_conversation_users_route: 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.
get_conversation_users_route 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_conversation_users_route 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_conversation_users_route. 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_conversation_users_route 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.
This server
Across the catalogue