get_agent_topics_route
Get Agent Conversation Topics.
This record as markdown: /tools/aiwerk-mcp-server-elevenlabs/get-agent-topics-route.md
What get_agent_topics_route does on Elevenlabs
AI agents call get_agent_topics_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. |
sort_by | string | — | Column to rank topics by. Use conversations for volume, sentiment with sort_direction=asc for the most negative topics, and frustration with sort_direction=desc |
agent_id | string | Yes | ID of the agent |
page_size | number | null | — | Number of top-level topic groups to return. |
to_unix_secs | number | null | — | End of the window to view topics for. |
from_unix_secs | number | null | — | Start of the window to view topics for. When set with to_unix_secs, the completed daily topic-discovery runs in the range are aggregated together, so the window |
sort_direction | string | — | Direction to sort topics. |
include_evaluation_criteria | boolean | — | Include the per-criteria evaluation breakdown on each topic's metrics. Pass false to drop it: it dominates the payload and the weighted success_rate is returned |
Parameters from the server's own tool schema.
Why get_agent_topics_route is rated Low
Even though get_agent_topics_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_agent_topics_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_agent_topics_route, this is the rule to start with:
get_agent_topics_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_agent_topics_route call is checked against it from then on.
Questions about get_agent_topics_route
Get Agent Conversation Topics. It is categorised as a Read tool in the Elevenlabs MCP Server, which means it retrieves data without modifying state.
get_agent_topics_route accepts 8 parameters: cursor, sort_by, agent_id, page_size, to_unix_secs, from_unix_secs, sort_direction, include_evaluation_criteria. Required: agent_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 get_agent_topics_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_agent_topics_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_agent_topics_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_agent_topics_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_agent_topics_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