list_agent_conversation_tickets_route

List Agent Conversation Tickets.

SERVERElevenlabs SOURCE@aiwerk/mcp-server-elevenlabs

Low RISK CLASS

Category Read

Parameters 101 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/aiwerk-mcp-server-elevenlabs/list-agent-conversation-tickets-route.md

WHAT IT DOES

What list_agent_conversation_tickets_route does on Elevenlabs

AI agents call list_agent_conversation_tickets_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
`label`	string \| null	—	Filter tickets by an exact label.
`cursor`	string \| null	—	Used for fetching next page. Cursor is returned in the response.
`status`	object	—	Filter tickets by status.
`sources`	object	—	Filter tickets by how they were raised (qa, agent, manual). Repeat the parameter to filter by multiple sources.
`agent_id`	string	Yes
`page_size`	number	—	How many agent conversation tickets to return. Can not exceed 100.
`issue_type`	object	—	Filter clusters by issue type.
`owner_user_id`	string \| null	—	Filter tickets by creator. Use 'agent' for agent-raised tickets.
`conversation_id`	string \| null	—	Filter tickets by conversation id.
`assignee_user_id`	string \| null	—	Filter tickets by assignee. Use 'unassigned' for tickets with no assignee.

Parameters from the server's own tool schema.

RISK

Why list_agent_conversation_tickets_route is rated Low

Even though list_agent_conversation_tickets_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 (10 properties)

Attacks that exploit this kind of access

RECOMMENDED RULE

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

list_agent_conversation_tickets_route Allowed

list_agent_conversation_tickets_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": {
    "list_agent_conversation_tickets_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 list_agent_conversation_tickets_route call is checked against it from then on.

FAQ

Questions about list_agent_conversation_tickets_route

What does the list_agent_conversation_tickets_route tool do? +

List Agent Conversation Tickets. It is categorised as a Read tool in the Elevenlabs MCP Server, which means it retrieves data without modifying state.

What parameters does list_agent_conversation_tickets_route accept? +

list_agent_conversation_tickets_route accepts 10 parameters: label, cursor, status, sources, agent_id, page_size, issue_type, owner_user_id, conversation_id, assignee_user_id. Required: agent_id. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on list_agent_conversation_tickets_route? +

Register the Elevenlabs MCP server in PolicyLayer and add a rule for list_agent_conversation_tickets_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 list_agent_conversation_tickets_route? +

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

Can I rate-limit list_agent_conversation_tickets_route? +

Yes. Add a rate_limit block to the list_agent_conversation_tickets_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 list_agent_conversation_tickets_route completely? +

Set action: deny in the PolicyLayer policy for list_agent_conversation_tickets_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 list_agent_conversation_tickets_route? +

list_agent_conversation_tickets_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

list_symbols on ACE-MCP →aiva_list_affiliates on AIVA MCP Server →list_circuits on 0gzk → The MCP Attack Database →

Guides

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