unpublish_document
Unpublish a document, removing its website and reverting to draft status.
This record as markdown: /tools/cloud-easybits-easybits/unpublish-document.md
What unpublish_document does on EasyBits
AI agents call unpublish_document to permanently remove resources in EasyBits, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why unpublish_document is rated Critical
Unpublishing removes public access to a document, which may be irreversible in practice.
From the tool's definition removing its website and reverting to draft status
Attacks that exploit this kind of access
The rule that runs unpublish_document safely
PolicyLayer is an MCP gateway: it sits between your AI agents and EasyBits, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For unpublish_document, this is the rule to start with:
unpublish_document is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect EasyBits, apply this rule, and every unpublish_document call is checked against it from then on.
Questions about unpublish_document
Unpublish a document, removing its website and reverting to draft status. It is categorised as a Destructive tool in the EasyBits MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the EasyBits MCP server in PolicyLayer and add a rule for unpublish_document: 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 EasyBits. Nothing to install.
unpublish_document is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the unpublish_document 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 unpublish_document. 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.
unpublish_document is provided by the EasyBits MCP server (@easybits.cloud/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on EasyBits, and thousands of servers like it.
Across the catalogue