Critical Risk →

version_unpublish_document

Mark a document to unpublish on release

Risk signalsSchedules content removal

Part of the Sanity server.

version_unpublish_document can permanently delete data in Sanity, with no limits today. PolicyLayer puts allow, deny, and rate-limit rules on every call. Live in minutes.

SECURE SANITY →

Free to start. No card required.

AI agents may call version_unpublish_document to permanently remove or destroy resources in Sanity. Without a policy, an autonomous agent could delete critical data in a loop with no way to undo the damage. PolicyLayer blocks destructive tools by default and requires explicit human approval before enabling them.

Without a policy, an AI agent could call version_unpublish_document in a loop, permanently destroying resources in Sanity. There is no undo for destructive operations. PolicyLayer blocks this tool by default and only allows it when a human explicitly approves the action.

Destructive tools permanently remove data. Block by default. Only enable with explicit approval workflows.

policy.json
{
  "version": "1",
  "default": "deny",
  "hide": [
    "version_unpublish_document"
  ]
}

See the full Sanity policy for all 36 tools.

Get this rule live on your own Sanity server in minutes. PolicyLayer enforces it on every call, before it runs.

ENFORCE ON MY SANITY →

View all 36 tools →

These attack patterns abuse exactly the kind of access version_unpublish_document gives an agent. Each links to the full case and the policy that stops it:

Browse the full MCP Attack Database →

Every attack above starts with a tool call. PolicyLayer checks each one against your policy first, so version_unpublish_document only ever does what you allow.

SECURE SANITY →

Other destructive tools across the catalogue. The same approach applies to each: deny by default, or require human approval.

What does the version_unpublish_document tool do? +

Mark a document to unpublish on release. It is categorised as a Destructive tool in the Sanity MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on version_unpublish_document? +

Register the Sanity MCP server in PolicyLayer and add a rule for version_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 Sanity. Nothing to install.

What risk level is version_unpublish_document? +

version_unpublish_document is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit version_unpublish_document? +

Yes. Add a rate_limit block to the version_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.

How do I block version_unpublish_document completely? +

Set action: deny in the PolicyLayer policy for version_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.

What MCP server provides version_unpublish_document? +

version_unpublish_document is provided by the Sanity MCP server (@@sanity/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Sanity tool call.

Deterministic rules across all 36 Sanity tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

4,600+ MCP servers and 31,000+ tools scanned and risk-classified.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.