transkribus_upload_create_from_mets
Create upload from METS file.
This record as markdown: /tools/io-github-lazyants-transkribus/transkribus-upload-create-from-mets.md
What transkribus_upload_create_from_mets does on Transkribus
AI agents use transkribus_upload_create_from_mets 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_upload_create_from_mets is rated Medium
This tool creates a new upload resource by parsing a METS (Metadata Encoding & Transmission Standard) file. This is a reversible write operation—the upload can be created and potentially undone through deletion, but the primary action is data creation/modification. It does not execute arbitrary code, is not destructive (the upload can be removed), and has no financial implications.
From the tool's definition Tool creates an upload from a METS file, which involves ingesting and registering data into the Transkribus system. The verb 'create' and the action of initializing an upload from external metadata indicate data modification.
Attacks that exploit this kind of access
The rule that runs transkribus_upload_create_from_mets 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_upload_create_from_mets, this is the rule to start with:
transkribus_upload_create_from_mets 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_upload_create_from_mets call is checked against it from then on.
Questions about transkribus_upload_create_from_mets
Create upload from METS file. 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_upload_create_from_mets: 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_upload_create_from_mets 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_upload_create_from_mets 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_upload_create_from_mets. 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_upload_create_from_mets 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