Append raw AppFlowy document blocks to the end of a page.
AI agents use appflowy_append_blocks_to_page 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.
This tool creates or modifies page content reversibly by appending blocks to a page. It does not execute code, delete data, or move money. The 'append' operation is reversible (content can be removed). Severity is medium because uncontrolled appending could spam pages or inject unwanted content into documents, but damage is not permanent or system-wide.
From the tool's definition Tool description states 'Append raw AppFlowy document blocks to the end of a page' — the verb 'append' indicates modification of existing content.
Attacks that exploit this kind of access
Append raw AppFlowy document blocks to the end of a page. 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_append_blocks_to_page: 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_append_blocks_to_page 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_append_blocks_to_page 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_append_blocks_to_page. 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_append_blocks_to_page 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 →