transkribus_recog_compute_sample
Compute a recognition sample for a document in a collection.
This record as markdown: /tools/io-github-lazyants-transkribus/transkribus-recog-compute-sample.md
What transkribus_recog_compute_sample does on Transkribus
AI agents invoke transkribus_recog_compute_sample 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_recog_compute_sample is rated High
This tool triggers an external computation (HTR/OCR recognition) on a document, which is an active processing operation rather than a simple read. It executes a recognition pipeline with side effects (producing output/results stored server-side). No irreversible destruction or financial implications, so Execute is the most severe applicable category.
From the tool's definition 'Compute a recognition sample' — triggers an HTR/OCR recognition computation operation on a document
Attacks that exploit this kind of access
The rule that runs transkribus_recog_compute_sample 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_recog_compute_sample, this is the rule to start with:
transkribus_recog_compute_sample 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_recog_compute_sample call is checked against it from then on.
Questions about transkribus_recog_compute_sample
Compute a recognition sample for a document in a collection. 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_recog_compute_sample: 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_recog_compute_sample 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_recog_compute_sample 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_recog_compute_sample. 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_recog_compute_sample 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