transkribus_label_remove_all_documents
Remove all documents from a label.
This record as markdown: /tools/io-github-lazyants-transkribus/transkribus-label-remove-all-documents.md
What transkribus_label_remove_all_documents does on Transkribus
AI agents call transkribus_label_remove_all_documents to permanently remove resources in Transkribus, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why transkribus_label_remove_all_documents is rated Critical
The tool performs a destructive action that cannot be undone: it removes (deletes) all documents associated with a label in a batch operation. This falls under Destructive rather than Write because removal is irreversible and affects multiple records simultaneously. The blast radius is high if an AI agent misclassifies what 'all documents' means or executes this unintentionally on the wrong label.
From the tool's definition Tool name contains 'remove' and description states 'Remove all documents from a label' — this is an irreversible bulk deletion operation affecting potentially many documents.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs transkribus_label_remove_all_documents safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Transkribus, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For transkribus_label_remove_all_documents, this is the rule to start with:
transkribus_label_remove_all_documents 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 Transkribus, apply this rule, and every transkribus_label_remove_all_documents call is checked against it from then on.
Questions about transkribus_label_remove_all_documents
Remove all documents from a label. It is categorised as a Destructive tool in the Transkribus MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Transkribus MCP server in PolicyLayer and add a rule for transkribus_label_remove_all_documents: 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 Transkribus. Nothing to install.
transkribus_label_remove_all_documents 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 transkribus_label_remove_all_documents 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 transkribus_label_remove_all_documents. 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.
transkribus_label_remove_all_documents is provided by the Transkribus MCP server (@lazyants/transkribus-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Transkribus, and thousands of servers like it.
Across the catalogue