add_knowledge_text
Add a free-form text document to the knowledge base. Use for pasted policies, FAQs, internal notes, brand voice references — anything the agent should be able to retrieve later. Stored as a single document; agent-side embedding/retrieval happens elsewhere.
This record as markdown: /tools/io-favcrm-favcrm/add-knowledge-text.md
What add_knowledge_text does on FavCRM
AI agents use add_knowledge_text to create or update resources in FavCRM, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your FavCRM environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
name | string | Yes | Friendly title for the document |
content | string | Yes | Document body text |
Parameters from the server's own tool schema.
Why add_knowledge_text is rated Medium
This tool creates or stores new data (a text document) in a knowledge base, which is a reversible write operation. There are no destructive effects (deletion/overwriting), no code execution, and no financial transactions. The blast radius is low — an agent adding unwanted or incorrect text to the knowledge base is recoverable by editing or deleting that document later.
From the tool's definition "Add a free-form text document to the knowledge base" — creates and stores new text data in a knowledge base without destructive or financial implications.
Risk signalsAccepts raw HTML/template content (content)
Attacks that exploit this kind of access
The rule that runs add_knowledge_text safely
PolicyLayer is an MCP gateway: it sits between your AI agents and FavCRM, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For add_knowledge_text, this is the rule to start with:
add_knowledge_text 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 FavCRM, apply this rule, and every add_knowledge_text call is checked against it from then on.
Questions about add_knowledge_text
Add a free-form text document to the knowledge base. Use for pasted policies, FAQs, internal notes, brand voice references — anything the agent should be able to retrieve later. Stored as a single document; agent-side embedding/retrieval happens elsewhere. It is categorised as a Write tool in the FavCRM MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
add_knowledge_text accepts 2 parameters: name, content. Required: name, content. The full parameter table on this page comes from the server's own tool schema.
Register the FavCRM MCP server in PolicyLayer and add a rule for add_knowledge_text: 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 FavCRM. Nothing to install.
add_knowledge_text 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_knowledge_text 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_knowledge_text. 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_knowledge_text is provided by the FavCRM MCP server (https://api.favcrm.io/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on FavCRM, and thousands of servers like it.
This server
Across the catalogue