Semantic search in documents.
AI agents call appflowy_search_documents to retrieve information from AppFlowy Cloud MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a search operation over documents, which is a read-only action that retrieves information without side effects. It does not create, modify, delete, or execute any operations. The semantic search capability is a passive query mechanism, making it the lowest-risk category.
From the tool's definition Tool name 'appflowy_search_documents' and description 'Semantic search in documents' indicate retrieval and querying of data without modification or execution of external operations.
Attacks that exploit this kind of access
Semantic search in documents. It is categorised as a Read tool in the AppFlowy Cloud MCP Server MCP Server, which means it retrieves data without modifying state.
Register the AppFlowy Cloud MCP Server MCP server in PolicyLayer and add a rule for appflowy_search_documents: 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 AppFlowy Cloud MCP Server. Nothing to install.
appflowy_search_documents 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 appflowy_search_documents 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 appflowy_search_documents. 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.
appflowy_search_documents is provided by the AppFlowy Cloud MCP Server MCP server (jemo69/appflowy-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →