This record as markdown: /tools/aiwerk-mcp-server-elevenlabs/public-list-orders.md
What public_list_orders does on Elevenlabs
AI agents call public_list_orders 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 |
|---|---|---|---|
offset | number | — | Number of orders to skip for pagination. |
status | object | — | Filter orders by one or more statuses. |
end_date | string | null | — | Filter orders created on or before this date. |
page_size | number | — | Maximum number of orders to return per page. |
start_date | string | null | — | Filter orders created on or after this date. |
Parameters from the server's own tool schema.
Why public_list_orders is rated Low
Even though public_list_orders 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 public_list_orders 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 public_list_orders, this is the rule to start with:
public_list_orders 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 public_list_orders call is checked against it from then on.
Questions about public_list_orders
List Orders. It is categorised as a Read tool in the Elevenlabs MCP Server, which means it retrieves data without modifying state.
public_list_orders accepts 5 parameters: offset, status, end_date, page_size, start_date. 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 public_list_orders: 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.
public_list_orders 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 public_list_orders 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 public_list_orders. 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.
public_list_orders 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