This record as markdown: /tools/aiwerk-mcp-server-elevenlabs/get-agents-route.md
What get_agents_route does on Elevenlabs
AI agents call get_agents_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 |
|---|---|---|---|
tags | object | — | Filter agents by tag. Repeat the parameter to match any of several tags. |
cursor | string | null | — | Used for fetching next page. Cursor is returned in the response. |
search | string | null | — | Search by agents name. |
sort_by | object | — | The field to sort the results by |
archived | boolean | null | — | Filter agents by archived status |
page_size | number | — | How many Agents to return at maximum. Can not exceed 100, defaults to 30. |
sort_direction | string | — | The direction to sort the results |
created_by_user_id | string | null | — | Filter agents by creator user ID. When set, only agents created by this user are returned. Takes precedence over show_only_owned_agents. Use '@me' to refer to t |
show_only_owned_agents | boolean | — | If set to true, the endpoint will omit any agents that were shared with you by someone else and include only the ones you own. Deprecated: use created_by_user_i |
Parameters from the server's own tool schema.
Why get_agents_route is rated Low
Even though get_agents_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_agents_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_agents_route, this is the rule to start with:
get_agents_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_agents_route call is checked against it from then on.
Questions about get_agents_route
List Agents. It is categorised as a Read tool in the Elevenlabs MCP Server, which means it retrieves data without modifying state.
get_agents_route accepts 9 parameters: tags, cursor, search, sort_by, archived, page_size, sort_direction, created_by_user_id, show_only_owned_agents. 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_agents_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_agents_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_agents_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_agents_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_agents_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