Permanently delete a trashed page.
AI agents call appflowy_delete_page_from_trash to permanently remove resources in AppFlowy MCP — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool irreversibly removes data from the system. Even though the page is already in trash (soft-delete state), this operation performs a permanent hard-delete that destroys the data completely. This cannot be reversed and represents the highest risk for data loss in the Destructive category.
From the tool's definition Tool name includes 'delete' and description states 'Permanently delete a trashed page' — the word 'Permanently' indicates irreversible deletion that cannot be undone.
Attacks that exploit this kind of access
Permanently delete a trashed page. It is categorised as a Destructive tool in the AppFlowy MCP MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the AppFlowy MCP server in PolicyLayer and add a rule for appflowy_delete_page_from_trash: 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_delete_page_from_trash is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the appflowy_delete_page_from_trash 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_delete_page_from_trash. 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_delete_page_from_trash 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 →