transkribus_page_get
Get details of a specific page in a document.
This record as markdown: /tools/io-github-lazyants-transkribus/transkribus-page-get.md
What transkribus_page_get does on Transkribus
AI agents call transkribus_page_get to retrieve information from Transkribus without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why transkribus_page_get is rated Low
This tool retrieves metadata or content about a page without creating, modifying, deleting, or executing any operations. It is a straightforward query/fetch operation, which falls under the Read category with low severity.
From the tool's definition Tool name 'transkribus_page_get' and description 'Get details of a specific page in a document' indicate a retrieval operation with no modification or side effects.
Attacks that exploit this kind of access
The rule that runs transkribus_page_get 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_get, this is the rule to start with:
transkribus_page_get is read-only, so it stays allowed. 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_get call is checked against it from then on.
Questions about transkribus_page_get
Get details of a specific page in a document. It is categorised as a Read tool in the Transkribus MCP Server, which means it retrieves data without modifying state.
Register the Transkribus MCP server in PolicyLayer and add a rule for transkribus_page_get: 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_get is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the transkribus_page_get 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_get. 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_get 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