transkribus_job_wait

Poll a job until it reaches FINISHED, FAILED or CANCELED, or until the wait budget runs out.

SERVERTranskribus SOURCE@lazyants/transkribus-mcp-server

High RISK CLASS

Category Execute

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-lazyants-transkribus/transkribus-job-wait.md

WHAT IT DOES

What transkribus_job_wait does on Transkribus

AI agents invoke transkribus_job_wait 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.

RISK

Why transkribus_job_wait is rated High

Waiting for job completion is an execute operation that monitors external process state and blocks until completion.

From the tool's definition Poll a job until it reaches FINISHED, FAILED or CANCELED

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs transkribus_job_wait 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_wait, this is the rule to start with:

transkribus_job_wait Rate-limited

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

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "transkribus_job_wait": {
      "limits": [
        {
          "counter": "transkribus_job_wait_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Transkribus, apply this rule, and every transkribus_job_wait call is checked against it from then on.

FAQ

Questions about transkribus_job_wait

What does the transkribus_job_wait tool do? +

Poll a job until it reaches FINISHED, FAILED or CANCELED, or until the wait budget runs out. 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.

How do I enforce a policy on transkribus_job_wait? +

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

transkribus_job_wait is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit transkribus_job_wait? +

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

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

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

KEEP EXPLORING

More on Transkribus, and thousands of servers like it.

This server

All 306 Transkribus tools → High-risk tools on this server →

Across the catalogue

browser_wait_for_element on Percepta MCP Server →wait_for_renders on Why Did You Render →qt_wait_for on Qt → All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →