transkribus_coll_delete
Delete a collection by ID.
This record as markdown: /tools/io-github-lazyants-transkribus/transkribus-coll-delete.md
What transkribus_coll_delete does on Transkribus
AI agents call transkribus_coll_delete 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_coll_delete is rated Critical
Deletion of a collection is an irreversible destructive operation that cannot be undone. It destroys data at scale (all documents and metadata within the collection). This matches the Destructive category definition: 'irreversibly deletes or overwrites data, or actions that cannot be undone.' Severity is high because the blast radius is a complete collection of documents, though not financial in nature.
From the tool's definition Tool name explicitly states 'delete' and description states 'Delete a collection by ID' — this irreversibly removes an entire collection and its contents.
Attacks that exploit this kind of access
The rule that runs transkribus_coll_delete 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_coll_delete, this is the rule to start with:
transkribus_coll_delete 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_coll_delete call is checked against it from then on.
Questions about transkribus_coll_delete
Delete a collection by ID. 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_coll_delete: 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_coll_delete 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_coll_delete 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_coll_delete. 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_coll_delete 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