Publish a page to the web so anyone with the link can view it.
AI agents use appflowy_publish_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.
Publishing a page modifies its access control state by changing visibility from private/restricted to publicly shareable. This is a reversible configuration change (the page can be unpublished), making it Write rather than Destructive.
From the tool's definition Tool name is 'appflowy_publish_page' and description states 'Publish a page to the web so anyone with the link can view it.' Publishing changes page visibility settings and makes content accessible to external parties, which is a modification of page…
Attacks that exploit this kind of access
Publish a page to the web so anyone with the link can view it. 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_publish_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_publish_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_publish_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_publish_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_publish_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 →