transkribus_crowd_delete_milestones
Delete milestones from the crowd project of a collection.
This record as markdown: /tools/io-github-lazyants-transkribus/transkribus-crowd-delete-milestones.md
What transkribus_crowd_delete_milestones does on Transkribus
AI agents call transkribus_crowd_delete_milestones 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_crowd_delete_milestones is rated Critical
The tool performs a delete operation that removes milestones, which is irreversible and permanent. This matches the Destructive category definition for actions that 'irreversibly deletes or overwrites data, or actions that cannot be undone.' While the blast radius is limited to project milestones (not entire collections), unauthorized deletion of project metadata could disrupt crowd-sourcing workflows and is a…
From the tool's definition Tool name contains 'delete' and description states 'Delete milestones from the crowd project of a collection.' The action is irreversible data removal.
Attacks that exploit this kind of access
The rule that runs transkribus_crowd_delete_milestones 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_crowd_delete_milestones, this is the rule to start with:
transkribus_crowd_delete_milestones 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_crowd_delete_milestones call is checked against it from then on.
Questions about transkribus_crowd_delete_milestones
Delete milestones from the crowd project of 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_crowd_delete_milestones: 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_crowd_delete_milestones 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_crowd_delete_milestones 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_crowd_delete_milestones. 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_crowd_delete_milestones 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