create_auth_connection
Create Workspace Auth Connection.
This record as markdown: /tools/aiwerk-mcp-server-elevenlabs/create-auth-connection.md
What create_auth_connection does on Elevenlabs
AI agents use create_auth_connection 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 | — | |
token | string | — | |
issuer | string | — | JWT issuer (iss claim) |
key_id | string | null | — | |
scopes | array | — | OAuth2 scopes to request when exchanging JWT for access token |
subject | string | — | JWT subject (sub claim) |
audience | string | — | JWT audience (aud claim) |
password | string | — | |
provider | string | — | |
username | string | — | |
algorithm | string | — | JWT signing algorithm |
auth_type | string | — |
Parameters from the server's own tool schema.
Why create_auth_connection is rated Medium
An AI agent can call create_auth_connection 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 signalsHandles credentials or secrets (token) · High parameter count (26 properties)
Attacks that exploit this kind of access
The rule that runs create_auth_connection 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 create_auth_connection, this is the rule to start with:
create_auth_connection 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Elevenlabs, apply this rule, and every create_auth_connection call is checked against it from then on.
Questions about create_auth_connection
Create Workspace Auth Connection. 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.
create_auth_connection accepts 12 parameters: name, token, issuer, key_id, scopes, subject, audience, password, provider, username, algorithm, auth_type. 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 create_auth_connection: 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.
create_auth_connection is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the create_auth_connection 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 create_auth_connection. 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.
create_auth_connection 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