cancel_checkout

THE RISK

Critical Risk

Why cancel_checkout needs a policy

Cancelling a checkout discards the working copy, which is an irreversible action — any unsaved changes in the working copy are permanently lost. This constitutes irreversible data destruction, making it Destructive rather than merely Write.

From the tool's definition Cancel checkout of a document, discarding any working copy

Documented attack patterns abuse exactly the kind of access cancel_checkout gives an agent:

POLICY

How to control cancel_checkout

PolicyLayer is an MCP gateway — it sits between your AI agents and Alfresco MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for cancel_checkout:

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "cancel_checkout"
  ]
}

cancel_checkout disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.

Create a free account and register Alfresco MCP Server — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

RESTRICT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Alfresco MCP Server tools

Destructive delete_node Delete a document or folder from Alfresco. Execute cmis_search Search using CMIS SQL syntax. Default query searches for PDF documents. Write checkin_document Check in a document after editing using Alfresco REST API. Write checkout_document Check out a document for editing using Alfresco REST API. Write create_folder Create a new folder in Alfresco. Write update_node_properties Update metadata and properties of a document or folder. Write upload_document Upload a document to Alfresco. Read advanced_search Advanced search with sorting and filtering capabilities.

All 15 Alfresco MCP Server tools →

Destructive tools on other servers

Android Forensics ADB MCP Server create_full_backup 0xarchive web3_revoke_key Frida Game Hacking MCP clear_scan cPanel MCP Server clear_spam_box

Go deeper

Critical-risk tools in Alfresco MCP Server → Every critical-risk tool this server exposes, in one view.
All critical-risk MCP tools → Every critical-risk tool across the catalogue, and the policy pattern that contains them.
The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Blast radius → How much damage one compromised or confused agent can do — and how to bound it.
Tool call approval → Approval gates on individual tool calls: auto-allow, prompt, or deny.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about cancel_checkout

What does the cancel_checkout tool do? +

Cancel checkout of a document, discarding any working copy. It is categorised as a Destructive tool in the Alfresco MCP Server 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 cancel_checkout? +

Register the Alfresco MCP Server MCP server in PolicyLayer and add a rule for cancel_checkout: 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 Alfresco MCP Server. Nothing to install.

What risk level is cancel_checkout? +

cancel_checkout 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 cancel_checkout? +

Yes. Add a rate_limit block to the cancel_checkout 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 cancel_checkout completely? +

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

cancel_checkout is provided by the Alfresco MCP Server MCP server (stevereiner/python-alfresco-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 Alfresco MCP Server tool call.

Start from Alfresco MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →