transkribus_page_lock
Lock or unlock a page for editing.
This record as markdown: /tools/io-github-lazyants-transkribus/transkribus-page-lock.md
What transkribus_page_lock does on Transkribus
AI agents use transkribus_page_lock 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_lock is rated Medium
Locking/unlocking pages modifies document state and affects concurrent access to editable resources, which is a Write operation (reversible state change). It is not Execute (no arbitrary code/commands), not Destructive (changes are reversible), and not Financial.
From the tool's definition Tool description states 'Lock or unlock a page for editing' — these are reversible state modifications that control access to data editing.
Attacks that exploit this kind of access
The rule that runs transkribus_page_lock 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_lock, this is the rule to start with:
transkribus_page_lock 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_lock call is checked against it from then on.
Questions about transkribus_page_lock
Lock or unlock a page for editing. 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_lock: 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_lock 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_lock 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_lock. 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_lock 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