transkribus_search_replace
Search for a term and replace it across documents.
This record as markdown: /tools/io-github-lazyants-transkribus/transkribus-search-replace.md
What transkribus_search_replace does on Transkribus
AI agents use transkribus_search_replace 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 is rated Medium
This tool modifies document content by replacing text across multiple documents. It is a bulk write operation that could affect many documents simultaneously, making misuse high severity. While potentially reversible depending on the platform's versioning, bulk text replacement across documents is categorized as Write.
From the tool's definition Search for a term and replace it across documents
Attacks that exploit this kind of access
The rule that runs transkribus_search_replace 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, this is the rule to start with:
transkribus_search_replace 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 call is checked against it from then on.
Questions about transkribus_search_replace
Search for a term and replace it across documents. 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: 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 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 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. 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 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