transkribus_editdecl_delete_option

Delete an option from an editorial declaration feature.

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-editdecl-delete-option.md

What transkribus_editdecl_delete_option does on Transkribus

AI agents call transkribus_editdecl_delete_option 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_editdecl_delete_option is rated Critical

The tool performs an irreversible deletion operation on editorial declaration data. Even though the scope is narrowed to a single option within a feature (rather than bulk deletion), deletion actions cannot be undone and constitute destructive operations. This is more severe than Write (which is reversible modification) and warrants the Destructive category.

From the tool's definition Tool name contains 'delete' and description states 'Delete an option from an editorial declaration feature' — irreversible removal of data.

Questions about transkribus_editdecl_delete_option

What does the transkribus_editdecl_delete_option tool do? +

Delete an option from an editorial declaration feature. 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_editdecl_delete_option? +

Register the Transkribus MCP server in PolicyLayer and add a rule for transkribus_editdecl_delete_option: 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_editdecl_delete_option? +

transkribus_editdecl_delete_option 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_editdecl_delete_option? +

Yes. Add a rate_limit block to the transkribus_editdecl_delete_option 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_editdecl_delete_option completely? +

Set action: deny in the PolicyLayer policy for transkribus_editdecl_delete_option. 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_editdecl_delete_option? +

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