add_documentation_to_knowledge_base
Add To Knowledge Base. Deprecated upstream.
This record as markdown: /tools/aiwerk-mcp-server-elevenlabs/add-documentation-to-knowledge-base.md
What add_documentation_to_knowledge_base does on Elevenlabs
AI agents use add_documentation_to_knowledge_base 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 |
|---|---|---|---|
url | string | — | URL to a page of documentation that the agent will have access to in order to interact with users. |
name | string | null | — | A custom, human-readable name for the document. |
agent_id | string | — | |
file_path | string | — | Documentation that the agent will have access to in order to interact with users. Local path. |
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 add_documentation_to_knowledge_base is rated Medium
An AI agent can call add_documentation_to_knowledge_base 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) · Accepts URL/endpoint input (url)
Attacks that exploit this kind of access
The rule that runs add_documentation_to_knowledge_base 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 add_documentation_to_knowledge_base, this is the rule to start with:
add_documentation_to_knowledge_base 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 add_documentation_to_knowledge_base call is checked against it from then on.
Questions about add_documentation_to_knowledge_base
Add To Knowledge Base. Deprecated upstream. 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.
add_documentation_to_knowledge_base accepts 6 parameters: url, name, agent_id, file_path, file_base64, file_filename. 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 add_documentation_to_knowledge_base: 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.
add_documentation_to_knowledge_base 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 add_documentation_to_knowledge_base 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 add_documentation_to_knowledge_base. 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.
add_documentation_to_knowledge_base 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