transkribus_search_replace_in_collection
Search for a term and replace it within a specific collection.
This record as markdown: /tools/io-github-lazyants-transkribus/transkribus-search-replace-in-collection.md
What transkribus_search_replace_in_collection does on Transkribus
AI agents use transkribus_search_replace_in_collection to create or update resources in Transkribus, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Transkribus environment.
Why transkribus_search_replace_in_collection is rated Medium
This tool modifies existing document content by replacing text across an entire collection. It is a Write operation (reversible in principle, but high blast radius since it can alter many documents at once across a full collection). It does not irreversibly delete data, so Destructive is not warranted, but misuse could corrupt large amounts of transcription data.
From the tool's definition Search for a term and replace it within a specific collection
Attacks that exploit this kind of access
The rule that runs transkribus_search_replace_in_collection 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_search_replace_in_collection, this is the rule to start with:
transkribus_search_replace_in_collection stays usable, but capped: an agent stuck in a loop can't make hundreds of changes 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_search_replace_in_collection call is checked against it from then on.
Questions about transkribus_search_replace_in_collection
Search for a term and replace it within a specific collection. It is categorised as a Write tool in the Transkribus MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Transkribus MCP server in PolicyLayer and add a rule for transkribus_search_replace_in_collection: 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_search_replace_in_collection is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the transkribus_search_replace_in_collection 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_search_replace_in_collection. 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_search_replace_in_collection 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.
This server
Across the catalogue