upload_asset
A write tool on the Elevenlabs MCP server.
This record as markdown: /tools/aiwerk-mcp-server-elevenlabs/upload-asset.md
What upload_asset does on Elevenlabs
AI agents use upload_asset 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 | Yes | Display name for the asset. |
asset_path | string | — | The file to upload. Local path. Required for this call. |
asset_base64 | string | — | Base64 contents for "asset". Use this when the server cannot read your local disk. |
asset_filename | string | — | Filename to send for "asset". Some endpoints infer the audio format from it. |
Parameters from the server's own tool schema.
Why upload_asset is rated Medium
An AI agent can call upload_asset 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.
Attacks that exploit this kind of access
The rule that runs upload_asset 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 upload_asset, this is the rule to start with:
upload_asset 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 upload_asset call is checked against it from then on.
Questions about upload_asset
upload_asset is a write tool on the Elevenlabs MCP server. 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.
upload_asset accepts 4 parameters: name, asset_path, asset_base64, asset_filename. Required: name. 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 upload_asset: 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.
upload_asset 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 upload_asset 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 upload_asset. 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.
upload_asset 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