transkribus_model_delete_by_type

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

Questions about transkribus_model_delete_by_type

What does the transkribus_model_delete_by_type tool do? +

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.

How do I enforce a policy on transkribus_model_delete_by_type? +

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.

What risk level is transkribus_model_delete_by_type? +

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.

Can I rate-limit transkribus_model_delete_by_type? +

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.

How do I block transkribus_model_delete_by_type completely? +

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.

What MCP server provides transkribus_model_delete_by_type? +

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.

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