transkribus_admin_rebuild_models_index
Rebuild the search index for all recognition models.
This record as markdown: /tools/io-github-lazyants-transkribus/transkribus-admin-rebuild-models-index.md
What transkribus_admin_rebuild_models_index does on Transkribus
AI agents invoke transkribus_admin_rebuild_models_index 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_admin_rebuild_models_index is rated High
Rebuilding a search index is an active operation that reprocesses/reindexes all recognition models system-wide. It is not a simple read, nor does it permanently delete data, but it triggers a potentially long-running administrative execution that affects all models. If misused, it could cause performance degradation or temporary unavailability of the search index during rebuild, hence high severity.
From the tool's definition 'Rebuild the search index for all recognition models' — triggers an administrative rebuild operation across all models
Attacks that exploit this kind of access
The rule that runs transkribus_admin_rebuild_models_index 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_admin_rebuild_models_index, this is the rule to start with:
transkribus_admin_rebuild_models_index 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_admin_rebuild_models_index call is checked against it from then on.
Questions about transkribus_admin_rebuild_models_index
Rebuild the search index for all recognition models. 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_admin_rebuild_models_index: 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_admin_rebuild_models_index 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_admin_rebuild_models_index 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_admin_rebuild_models_index. 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_admin_rebuild_models_index 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