transkribus_coll_find_documents_post
Search for documents across collections using a POST request body.
This record as markdown: /tools/io-github-lazyants-transkribus/transkribus-coll-find-documents-post.md
What transkribus_coll_find_documents_post does on Transkribus
AI agents call transkribus_coll_find_documents_post 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_coll_find_documents_post is rated Low
This tool retrieves and queries documents matching search criteria. It has no side effects—it does not create, modify, delete, or execute operations. While it uses POST, the semantics are clearly for information retrieval. The blast radius is minimal: at worst, an agent could search for sensitive documents, but cannot access their contents without additional tools, nor modify any data.
From the tool's definition Tool name contains 'find_documents' and description states 'Search for documents across collections'. The POST method is used here for query parameters in the request body (a common REST API pattern for complex search queries), not for creating or modifying…
Attacks that exploit this kind of access
The rule that runs transkribus_coll_find_documents_post 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_coll_find_documents_post, this is the rule to start with:
transkribus_coll_find_documents_post 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_coll_find_documents_post call is checked against it from then on.
Questions about transkribus_coll_find_documents_post
Search for documents across collections using a POST request 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_coll_find_documents_post: 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_coll_find_documents_post 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_coll_find_documents_post 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_coll_find_documents_post. 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_coll_find_documents_post 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