This record as markdown: /tools/aiwerk-mcp-server-elevenlabs/get-livekit-token.md
What get_livekit_token does on Elevenlabs
AI agents call get_livekit_token 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 |
|---|---|---|---|
agent_id | string | Yes | Agent id (agent_…) or speech engine external id (seng_), resolved to the same underlying resource. |
branch_id | string | null | — | The ID of the branch to use |
version_id | string | null | — | The ID of the version to use |
environment | string | null | — | The environment to use for resolving environment variables (e.g. 'production', 'staging'). Defaults to 'production'. |
participant_name | string | null | — | Optional custom participant name. If not provided, user ID will be used |
debug_events_request | boolean | — | Whether to enable debug events. Only available for users with editor access to the agent. |
Parameters from the server's own tool schema.
Why get_livekit_token is rated Low
Even though get_livekit_token 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_livekit_token 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_livekit_token, this is the rule to start with:
get_livekit_token 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_livekit_token call is checked against it from then on.
Questions about get_livekit_token
Get Webrtc Token. It is categorised as a Read tool in the Elevenlabs MCP Server, which means it retrieves data without modifying state.
get_livekit_token accepts 6 parameters: agent_id, branch_id, version_id, environment, participant_name, debug_events_request. Required: agent_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_livekit_token: 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_livekit_token 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_livekit_token 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_livekit_token. 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_livekit_token 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