transkribus_stat_get_pages_filtered
Get collection pages with filtering via POST body.
This record as markdown: /tools/io-github-lazyants-transkribus/transkribus-stat-get-pages-filtered.md
What transkribus_stat_get_pages_filtered does on Transkribus
AI agents call transkribus_stat_get_pages_filtered 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_stat_get_pages_filtered is rated Low
This tool queries and retrieves paginated collection data with optional filters. There is no indication it modifies, deletes, or executes external operations. The use of POST for filtering is a standard REST convention for complex read queries and does not elevate the category to Write or Execute.
From the tool's definition Tool name contains 'get' and description states 'Get collection pages with filtering' — retrieves data with no modification or deletion. The POST method is used for query filtering (common REST pattern), not for side effects.
Attacks that exploit this kind of access
The rule that runs transkribus_stat_get_pages_filtered 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_stat_get_pages_filtered, this is the rule to start with:
transkribus_stat_get_pages_filtered 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_stat_get_pages_filtered call is checked against it from then on.
Questions about transkribus_stat_get_pages_filtered
Get collection pages with filtering via POST body. 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_stat_get_pages_filtered: 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_stat_get_pages_filtered 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_stat_get_pages_filtered 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_stat_get_pages_filtered. 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_stat_get_pages_filtered 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