update_agent_response_test_route

Update Agent Response Test.

SERVERElevenlabs SOURCE@aiwerk/mcp-server-elevenlabs

Medium RISK CLASS

Category Write

Parameters 121 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/aiwerk-mcp-server-elevenlabs/update-agent-response-test-route.md

WHAT IT DOES

What update_agent_response_test_route does on Elevenlabs

AI agents use update_agent_response_test_route to create or update resources in Elevenlabs, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Elevenlabs environment.

Parameter	Type	Required	Description
`name`	string	—
`type`	string	—
`test_id`	string	Yes	The id of a chat response test. This is returned on test creation.
`environment`	string \| null	—
`chat_history`	array	—
`evaluation_model`	object	—
`failure_examples`	array	—	Non-empty list of example responses that should be considered failures
`parent_folder_id`	string \| null	—
`success_examples`	array	—	Non-empty list of example responses that should be considered successful
`tool_mock_config`	object	—	Simulation/preview-side config: tools are identified by IDs, resolved to names at runtime.
`dynamic_variables`	object	—	Dynamic variables to replace in the agent config during testing
`success_condition`	string \| null	—

Parameters from the server's own tool schema.

RISK

Why update_agent_response_test_route is rated Medium

An AI agent can call update_agent_response_test_route faster than any human can review: one bad instruction and it creates or modifies resources in Elevenlabs by the hundred, each call as confident as the last.

Risk signalsHigh parameter count (25 properties)

Attacks that exploit this kind of access

RECOMMENDED RULE

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

update_agent_response_test_route Rate-limited

update_agent_response_test_route stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "update_agent_response_test_route": {
      "limits": [
        {
          "counter": "update_agent_response_test_route_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about update_agent_response_test_route

What does the update_agent_response_test_route tool do? +

Update Agent Response Test. It is categorised as a Write tool in the Elevenlabs MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

What parameters does update_agent_response_test_route accept? +

update_agent_response_test_route accepts 12 parameters: name, type, test_id, environment, chat_history, evaluation_model, failure_examples, parent_folder_id, success_examples, tool_mock_config, dynamic_variables, success_condition. Required: test_id. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on update_agent_response_test_route? +

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

update_agent_response_test_route is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit update_agent_response_test_route? +

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

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

update_agent_response_test_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

aroflo_create_or_update_record on AroFlo MCP →team_manager_kill_agent on Team Manager MCP → The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →