transkribus_recog_run_trhtr

Run TRHTR recognition using a specific model in a collection.

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-recog-run-trhtr.md

WHAT IT DOES

What transkribus_recog_run_trhtr does on Transkribus

AI agents invoke transkribus_recog_run_trhtr 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_recog_run_trhtr is rated High

This tool executes a recognition algorithm (TRHTR) on document content. Execution tools trigger external operations whose side effects depend on arguments. While not destructive or write-oriented (it doesn't permanently modify the source documents), it initiates a compute job that processes data and generates recognition results.

From the tool's definition Tool description states 'Run TRHTR recognition' — the verb 'run' indicates execution of a handwriting/text recognition operation on documents in a collection.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

transkribus_recog_run_trhtr Rate-limited

transkribus_recog_run_trhtr 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_recog_run_trhtr": {
      "limits": [
        {
          "counter": "transkribus_recog_run_trhtr_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_recog_run_trhtr call is checked against it from then on.

FAQ

Questions about transkribus_recog_run_trhtr

What does the transkribus_recog_run_trhtr tool do? +

Run TRHTR recognition using a specific model 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.

How do I enforce a policy on transkribus_recog_run_trhtr? +

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

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

Can I rate-limit transkribus_recog_run_trhtr? +

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

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

transkribus_recog_run_trhtr 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 301 Transkribus tools → High-risk tools on this server →

Across the catalogue

shortcuts_run on Apple Apps MCP →run_emba_scan on EMBA-MCP → All high-risk MCP tools → The MCP Attack Database →

Guides

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