forced_alignment
Create Forced Alignment. Spends ElevenLabs credits.
This record as markdown: /tools/aiwerk-mcp-server-elevenlabs/forced-alignment.md
What forced_alignment does on Elevenlabs
AI agents use forced_alignment 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 |
|---|---|---|---|
text | string | Yes | The text to align with the audio. The input text can be in any format, however diarization is not supported at this time. |
file_path | string | — | The file to align. All major audio formats are supported. The file size must be less than 1GB. Local path. Required for this call. |
file_base64 | string | — | Base64 contents for "file". Use this when the server cannot read your local disk. |
file_filename | string | — | Filename to send for "file". Some endpoints infer the audio format from it. |
Parameters from the server's own tool schema.
Why forced_alignment is rated Medium
An AI agent can call forced_alignment 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 signalsAccepts file system path (file_path)
Attacks that exploit this kind of access
The rule that runs forced_alignment 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 forced_alignment, this is the rule to start with:
forced_alignment 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 forced_alignment call is checked against it from then on.
Questions about forced_alignment
Create Forced Alignment. Spends ElevenLabs credits. 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.
forced_alignment accepts 4 parameters: text, file_path, file_base64, file_filename. Required: text. 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 forced_alignment: 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.
forced_alignment 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 forced_alignment 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 forced_alignment. 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.
forced_alignment 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