get_knowledge_document
Fetch a single knowledge document with metadata + extraction/review status. Reviewed content is served via GET /v6/merchant/ai/knowledge/{id}/content; raw/extracted variants are for audit.
This record as markdown: /tools/io-favcrm-favcrm/get-knowledge-document.md
What get_knowledge_document does on FavCRM
AI agents call get_knowledge_document to retrieve information from FavCRM without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
documentId | string | Yes | Knowledge document ID |
Parameters from the server's own tool schema.
Why get_knowledge_document is rated Low
This tool retrieves and serves existing knowledge document content and metadata without any side effects. It returns different variants (reviewed, raw, extracted) for audit purposes, but does not create, modify, delete, or execute any operations. This is a straightforward read/fetch operation with minimal security risk if misused by an AI agent.
From the tool's definition Tool description states 'Fetch a single knowledge document' — a retrieval operation with no modification, creation, or deletion. The description emphasizes fetching metadata and status information, consistent with a read-only query.
Attacks that exploit this kind of access
The rule that runs get_knowledge_document 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 get_knowledge_document, this is the rule to start with:
get_knowledge_document is read-only, so it stays allowed. 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 get_knowledge_document call is checked against it from then on.
Questions about get_knowledge_document
Fetch a single knowledge document with metadata + extraction/review status. Reviewed content is served via GET /v6/merchant/ai/knowledge/{id}/content; raw/extracted variants are for audit. It is categorised as a Read tool in the FavCRM MCP Server, which means it retrieves data without modifying state.
get_knowledge_document accepts 1 parameter: documentId. Required: documentId. 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 get_knowledge_document: 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.
get_knowledge_document is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_knowledge_document 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 get_knowledge_document. 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.
get_knowledge_document 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