transkribus_model_delete_by_type
Delete a model by its type and ID.
This record as markdown: /tools/io-github-lazyants-transkribus/transkribus-model-delete-by-type.md
What transkribus_model_delete_by_type does on Transkribus
AI agents call transkribus_model_delete_by_type 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_model_delete_by_type is rated Critical
The tool directly deletes data (a model) based on type and ID parameters. Deletion is an irreversible action that destroys data and cannot be recovered, making it Destructive rather than merely Write. The severity is high because loss of a trained model in an AI/ML context (Transkribus specializes in HTR/OCR models) represents significant data loss and potential disruption to document processing workflows.
From the tool's definition The tool name explicitly contains 'delete' and the description states 'Delete a model by its type and ID.' This is an irreversible removal operation that cannot be undone.
Attacks that exploit this kind of access
The rule that runs transkribus_model_delete_by_type 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_model_delete_by_type, this is the rule to start with:
transkribus_model_delete_by_type 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_model_delete_by_type call is checked against it from then on.
Questions about transkribus_model_delete_by_type
Delete a model by its type and 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_model_delete_by_type: 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_model_delete_by_type 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_model_delete_by_type 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_model_delete_by_type. 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_model_delete_by_type 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