transkribus_model_delete

Delete a model by its ID.

SERVERTranskribus SOURCE@lazyants/transkribus-mcp-server
Critical RISK CLASS
Category Destructive
Parameters 00 required
Recommended Hiddensee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-lazyants-transkribus/transkribus-model-delete.md

What transkribus_model_delete does on Transkribus

AI agents call transkribus_model_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_model_delete is rated Critical

The tool performs an irreversible deletion of a model resource. Once deleted, the model cannot be recovered through normal means. This qualifies as Destructive rather than Write (which is reversible). The high severity reflects that an AI agent given this tool could permanently destroy valuable machine learning models or OCR/HTR models that users depend on, causing significant disruption.

From the tool's definition Tool name explicitly states 'delete' and description confirms 'Delete a model by its ID' — this is an irreversible operation that removes data permanently.

Questions about transkribus_model_delete

What does the transkribus_model_delete tool do? +

Delete a model by its 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.

How do I enforce a policy on transkribus_model_delete? +

Register the Transkribus MCP server in PolicyLayer and add a rule for transkribus_model_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.

What risk level is transkribus_model_delete? +

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

Yes. Add a rate_limit block to the transkribus_model_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.

How do I block transkribus_model_delete completely? +

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

What MCP server provides transkribus_model_delete? +

transkribus_model_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.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Transkribus's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.