This record as markdown: /tools/aiwerk-mcp-server-elevenlabs/get-tool-executions-route.md
What get_tool_executions_route does on Elevenlabs
AI agents call get_tool_executions_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. |
tool_id | string | Yes | ID of the requested tool. |
agent_id | string | null | — | Filter by agent ID. |
end_time | number | null | — | Filter executions until this Unix timestamp (inclusive). |
is_error | boolean | null | — | Filter by error status. If not provided, returns all executions. |
branch_id | string | null | — | Filter by agent branch ID. |
page_size | number | — | How many documents to return at maximum. Can not exceed 100, defaults to 30. |
start_time | number | null | — | Filter executions from this Unix timestamp (inclusive). |
Parameters from the server's own tool schema.
Why get_tool_executions_route is rated Low
Even though get_tool_executions_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_tool_executions_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_tool_executions_route, this is the rule to start with:
get_tool_executions_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_tool_executions_route call is checked against it from then on.
Questions about get_tool_executions_route
Get Tool Executions. It is categorised as a Read tool in the Elevenlabs MCP Server, which means it retrieves data without modifying state.
get_tool_executions_route accepts 8 parameters: cursor, tool_id, agent_id, end_time, is_error, branch_id, page_size, start_time. Required: tool_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_tool_executions_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_tool_executions_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_tool_executions_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_tool_executions_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_tool_executions_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