appflowy_export_page
AI agents call appflowy_export_page to retrieve information from AppFlowy MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The name 'export_page' strongly suggests a read/retrieval operation that extracts page content for external use. Export operations typically read data and produce an output without modifying the source. However, the empty description lowers confidence significantly since we cannot confirm there are no side effects. Severity is medium because exporting page content could expose sensitive information if misused.
From the tool's definition Tool name contains 'export', description is empty and uninformative
Attacks that exploit this kind of access
appflowy_export_page. It is categorised as a Read tool in the AppFlowy MCP MCP Server, which means it retrieves data without modifying state.
Register the AppFlowy MCP server in PolicyLayer and add a rule for appflowy_export_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_export_page is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the appflowy_export_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_export_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_export_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 →