Restore a page from trash.
AI agents use appflowy_restore_page_from_trash 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.
Restoring a page from trash modifies data state reversibly—the page's existence and visibility are changed, but the action can be undone by deleting again. This is characteristic of Write operations (create, update, modify). While it involves previously deleted data, restoration is not destructive in the sense of permanent deletion or data loss.
From the tool's definition Tool name 'appflowy_restore_page_from_trash' and description 'Restore a page from trash' indicate modification of page state by recovering previously deleted content.
Attacks that exploit this kind of access
Restore a page from trash. 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_restore_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_restore_page_from_trash 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_restore_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_restore_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_restore_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 →