transkribus_recog_remove_from_collection
Remove a recognition model from a collection.
This record as markdown: /tools/io-github-lazyants-transkribus/transkribus-recog-remove-from-collection.md
What transkribus_recog_remove_from_collection does on Transkribus
AI agents call transkribus_recog_remove_from_collection 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_recog_remove_from_collection is rated Critical
Removing a recognition model from a collection is a destructive action that cannot be easily undone. While the model itself may persist elsewhere, its association with the collection is permanently severed, potentially breaking workflows or making the model inaccessible to users who depend on that collection.
From the tool's definition Tool name contains 'remove' and description states 'Remove a recognition model from a collection' — this operation irreversibly deletes or detaches a model resource from a collection, preventing its future use.
Attacks that exploit this kind of access
The rule that runs transkribus_recog_remove_from_collection 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_recog_remove_from_collection, this is the rule to start with:
transkribus_recog_remove_from_collection 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_recog_remove_from_collection call is checked against it from then on.
Questions about transkribus_recog_remove_from_collection
Remove a recognition model from a collection. 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_recog_remove_from_collection: 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_recog_remove_from_collection 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_recog_remove_from_collection 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_recog_remove_from_collection. 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_recog_remove_from_collection 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