transkribus_label_replace_document_assignments
Replace label assignments for a specific document.
This record as markdown: /tools/io-github-lazyants-transkribus/transkribus-label-replace-document-assignments.md
What transkribus_label_replace_document_assignments does on Transkribus
AI agents use transkribus_label_replace_document_assignments to create or update resources in Transkribus, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Transkribus environment.
Why transkribus_label_replace_document_assignments is rated Medium
This tool modifies existing label assignments on a document. The operation is reversible (labels can be replaced again with different values), so it falls under Write rather than Destructive. The severity is medium because incorrect label assignments could affect document organization, retrieval, or downstream processing, but the change is not permanent and can be corrected.
From the tool's definition Tool name contains 'replace' and description states it will 'Replace label assignments for a specific document,' indicating reversible modification of metadata or labeling data associated with a document.
Attacks that exploit this kind of access
The rule that runs transkribus_label_replace_document_assignments 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_label_replace_document_assignments, this is the rule to start with:
transkribus_label_replace_document_assignments stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Transkribus, apply this rule, and every transkribus_label_replace_document_assignments call is checked against it from then on.
Questions about transkribus_label_replace_document_assignments
Replace label assignments for a specific document. It is categorised as a Write tool in the Transkribus MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Transkribus MCP server in PolicyLayer and add a rule for transkribus_label_replace_document_assignments: 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_label_replace_document_assignments is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the transkribus_label_replace_document_assignments 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_label_replace_document_assignments. 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_label_replace_document_assignments 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.
This server
Across the catalogue