appflowy_create_chat
AI agents use appflowy_create_chat to create or update resources in AppFlowy MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your AppFlowy MCP environment.
The 'create' prefix strongly suggests this tool creates a new chat entity (Write category). Based on sibling tools like appflowy_create_page and appflowy_create_markdown_page, 'create' tools on this server are Write operations. However, the empty description lowers confidence significantly. Severity is medium as creating chats could expose data or consume resources but is generally reversible.
From the tool's definition Tool name 'appflowy_create_chat' implies creation of a new chat resource. Description is empty and uninformative.
Attacks that exploit this kind of access
appflowy_create_chat. It is categorised as a Write tool in the AppFlowy MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the AppFlowy MCP server in PolicyLayer and add a rule for appflowy_create_chat: 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 MCP. Nothing to install.
appflowy_create_chat 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 appflowy_create_chat 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_create_chat. 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_create_chat is provided by the AppFlowy MCP server (weironz/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 →