transkribus_doc_move_pages_by_image_names
Move pages within a document based on image names.
This record as markdown: /tools/io-github-lazyants-transkribus/transkribus-doc-move-pages-by-image-names.md
What transkribus_doc_move_pages_by_image_names does on Transkribus
AI agents use transkribus_doc_move_pages_by_image_names 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_doc_move_pages_by_image_names is rated Medium
Moving pages within a document is a reversible modification (pages can be moved back to original positions), not a destructive deletion. It changes document state but does not irreversibly delete or create new data. The blast radius is medium because reordering pages could disrupt document workflows or integrity if done incorrectly by an AI agent, but the action is recoverable.
From the tool's definition Tool name contains 'move' and description states 'Move pages within a document based on image names' — this modifies the structure/ordering of document content.
Attacks that exploit this kind of access
The rule that runs transkribus_doc_move_pages_by_image_names 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_doc_move_pages_by_image_names, this is the rule to start with:
transkribus_doc_move_pages_by_image_names 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_doc_move_pages_by_image_names call is checked against it from then on.
Questions about transkribus_doc_move_pages_by_image_names
Move pages within a document based on image names. 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_doc_move_pages_by_image_names: 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_doc_move_pages_by_image_names 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_doc_move_pages_by_image_names 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_doc_move_pages_by_image_names. 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_doc_move_pages_by_image_names 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