transkribus_job_create
Create a new processing job.
This record as markdown: /tools/io-github-lazyants-transkribus/transkribus-job-create.md
What transkribus_job_create does on Transkribus
AI agents invoke transkribus_job_create to trigger actions in Transkribus. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
Why transkribus_job_create is rated High
Creating a processing job triggers external computation and operations on documents/models. This goes beyond a simple write (data creation) because it launches an active execution pipeline. Misuse could consume significant compute resources or process sensitive documents unintentionally, warranting high severity.
From the tool's definition "Create a new processing job" — initiates an external processing operation (HTR/OCR job execution) on the Transkribus platform
Attacks that exploit this kind of access
The rule that runs transkribus_job_create 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_job_create, this is the rule to start with:
transkribus_job_create stays usable, but rate-capped: a runaway agent can't fire it dozens of times 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_job_create call is checked against it from then on.
Questions about transkribus_job_create
Create a new processing job. It is categorised as a Execute tool in the Transkribus MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Transkribus MCP server in PolicyLayer and add a rule for transkribus_job_create: 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_job_create is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the transkribus_job_create 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_job_create. 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_job_create 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