Revoke public access for a page.
AI agents use appflowy_unpublish_page to create or update resources in AppFlowy Cloud MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your AppFlowy Cloud MCP Server environment.
Unpublishing a page revokes public access, which is a reversible modification of access settings. The page itself is not deleted — it can be republished. This is a Write operation (modifying access state), not Destructive since the content remains intact. Misuse could expose previously public content to become inaccessible to external users, which has moderate blast radius.
From the tool's definition Revoke public access for a page
Attacks that exploit this kind of access
Revoke public access for a page. It is categorised as a Write tool in the AppFlowy Cloud MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the AppFlowy Cloud MCP Server MCP server in PolicyLayer and add a rule for appflowy_unpublish_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 Cloud MCP Server. Nothing to install.
appflowy_unpublish_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_unpublish_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_unpublish_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_unpublish_page is provided by the AppFlowy Cloud MCP Server MCP server (jemo69/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 →