transkribus_page_update_status_v2
Update page status using transcript ID (alternative endpoint).
This record as markdown: /tools/io-github-lazyants-transkribus/transkribus-page-update-status-v2.md
What transkribus_page_update_status_v2 does on Transkribus
AI agents use transkribus_page_update_status_v2 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_page_update_status_v2 is rated Medium
This tool modifies the status field of a page document in the Transkribus system. Status updates are state changes that can be reversed by changing the status again, making this a Write operation rather than Destructive. The severity is medium because inadvertent status changes could affect document processing workflows and user expectations, but the impact is limited to metadata/state rather than data loss.
From the tool's definition Tool name contains 'update' and description states 'Update page status', indicating modification of existing data. The endpoint is reversible (status can be changed again), distinguishing it from destructive operations.
Attacks that exploit this kind of access
The rule that runs transkribus_page_update_status_v2 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_page_update_status_v2, this is the rule to start with:
transkribus_page_update_status_v2 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_page_update_status_v2 call is checked against it from then on.
Questions about transkribus_page_update_status_v2
Update page status using transcript ID (alternative endpoint). 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_page_update_status_v2: 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_page_update_status_v2 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_page_update_status_v2 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_page_update_status_v2. 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_page_update_status_v2 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