usage_characters
Get Characters Usage Metrics (Deprecated) Deprecated upstream.
This record as markdown: /tools/aiwerk-mcp-server-elevenlabs/usage-characters.md
What usage_characters does on Elevenlabs
AI agents call usage_characters 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 |
|---|---|---|---|
metric | string | — | Which metric to aggregate. |
end_unix | number | Yes | UTC Unix timestamp for the end of the usage window, in milliseconds. To include the last day of the window, the timestamp should be at 23:59:59 of that day. |
start_unix | number | Yes | UTC Unix timestamp for the start of the usage window, in milliseconds. To include the first day of the window, the timestamp should be at 00:00:00 of that day. |
breakdown_type | string | — | How to break down the information. Cannot be "user" if include_workspace_metrics is False. |
aggregation_interval | string | — | How to aggregate usage data over time. Can be "hour", "day", "week", "month", or "cumulative". |
aggregation_bucket_size | number | null | — | Aggregation bucket size in seconds. Overrides the aggregation interval. |
include_workspace_metrics | boolean | — | Whether or not to include the statistics of the entire workspace. |
Parameters from the server's own tool schema.
Why usage_characters is rated Low
Even though usage_characters 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 usage_characters 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 usage_characters, this is the rule to start with:
usage_characters 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 usage_characters call is checked against it from then on.
Questions about usage_characters
Get Characters Usage Metrics (Deprecated) Deprecated upstream. It is categorised as a Read tool in the Elevenlabs MCP Server, which means it retrieves data without modifying state.
usage_characters accepts 7 parameters: metric, end_unix, start_unix, breakdown_type, aggregation_interval, aggregation_bucket_size, include_workspace_metrics. Required: end_unix, start_unix. 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 usage_characters: 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.
usage_characters 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 usage_characters 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 usage_characters. 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.
usage_characters 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