list_chat_response_tests_route
List Agent Response Tests.
This record as markdown: /tools/aiwerk-mcp-server-elevenlabs/list-chat-response-tests-route.md
What list_chat_response_tests_route does on Elevenlabs
AI agents call list_chat_response_tests_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 |
|---|---|---|---|
types | object | — | If present, the endpoint will return only tests/folders of the given types. |
cursor | string | null | — | Used for fetching next page. Cursor is returned in the response. |
search | string | null | — | Search query to filter tests and folders by name. |
page_size | number | — | How many Tests to return at maximum. Can not exceed 100, defaults to 30. |
sort_mode | string | — | Sort mode for listing tests. Use 'folders_first' to place folders before tests. |
sharing_mode | string | — | Filter test visibility. Use `shared_with_me` to return only tests/folders shared with the current user that they did not create. |
include_folders | boolean | null | — | Deprecated. Use the `types` query param and include `folder` instead. |
parent_folder_id | string | null | — | Filter by parent folder ID. Use 'root' to get items in the root folder. |
Parameters from the server's own tool schema.
Why list_chat_response_tests_route is rated Low
Even though list_chat_response_tests_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 list_chat_response_tests_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_chat_response_tests_route, this is the rule to start with:
list_chat_response_tests_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 list_chat_response_tests_route call is checked against it from then on.
Questions about list_chat_response_tests_route
List Agent Response Tests. It is categorised as a Read tool in the Elevenlabs MCP Server, which means it retrieves data without modifying state.
list_chat_response_tests_route accepts 8 parameters: types, cursor, search, page_size, sort_mode, sharing_mode, include_folders, parent_folder_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 list_chat_response_tests_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.
list_chat_response_tests_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 list_chat_response_tests_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 list_chat_response_tests_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.
list_chat_response_tests_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