appflowy_move_page
AI agents use appflowy_move_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 modifies data (page location) reversibly. It does not delete data (would be Destructive), execute arbitrary code (would be Execute), or create new content (would be Write but less severe than moving). Moving pages is a structural modification with medium severity—an AI agent misusing this could reorganize content in confusing ways but the action can be undone.
From the tool's definition Tool name 'appflowy_move_page' indicates modification of page location/hierarchy within the workspace. The server description confirms capability for 'page management.' Moving a page reorganizes content structure but is reversible (pages can be moved again to…
Attacks that exploit this kind of access
appflowy_move_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_move_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_move_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_move_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_move_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_move_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 →