get_conversation_histories_route

Get Conversations.

SERVERElevenlabs SOURCE@aiwerk/mcp-server-elevenlabs

Low RISK CLASS

Category Read

Parameters 120 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/aiwerk-mcp-server-elevenlabs/get-conversation-histories-route.md

WHAT IT DOES

What get_conversation_histories_route does on Elevenlabs

AI agents call get_conversation_histories_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	—	Full-text or fuzzy search over transcript messages
`tag_ids`	object	—	Filter conversations by conversation tag IDs assigned via the conversation-tags endpoints.
`user_id`	string \| null	—	Filter conversations by the user ID who initiated them.
`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 conversations to return at maximum. Can not exceed 100, defaults to 30.
`text_only`	boolean \| null	—
`topic_ids`	object	—	Filter conversations by topic IDs assigned during topic discovery.
`rating_max`	number \| null	—	Maximum overall rating (1-5).
`rating_min`	number \| null	—	Minimum overall rating (1-5).
`tool_names`	object	—	Filter conversations by tool names used during the call.

Parameters from the server's own tool schema.

RISK

Why get_conversation_histories_route is rated Low

Even though get_conversation_histories_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.

Risk signalsHigh parameter count (41 properties)

Attacks that exploit this kind of access

RECOMMENDED RULE

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

get_conversation_histories_route Allowed

get_conversation_histories_route is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_conversation_histories_route": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about get_conversation_histories_route

What does the get_conversation_histories_route tool do? +

Get Conversations. It is categorised as a Read tool in the Elevenlabs MCP Server, which means it retrieves data without modifying state.

What parameters does get_conversation_histories_route accept? +

get_conversation_histories_route accepts 12 parameters: cursor, search, tag_ids, user_id, agent_id, branch_id, page_size, text_only, topic_ids, rating_max, rating_min, tool_names. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on get_conversation_histories_route? +

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

What risk level is get_conversation_histories_route? +

get_conversation_histories_route is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_conversation_histories_route? +

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

How do I block get_conversation_histories_route completely? +

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

What MCP server provides get_conversation_histories_route? +

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

KEEP EXPLORING

More on Elevenlabs, and thousands of servers like it.

This server

All 390 Elevenlabs tools →

Across the catalogue

get_cocktail_by_category on Cocktails RAG MCP Server →get_file_snippet on ACE-MCP →get_torrent_detail on M-Team MCP Server →aiva_get_affiliate on AIVA MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →