transkribus_model_add_collection_by_id
Add a collection to a model by model ID and collection ID.
This record as markdown: /tools/io-github-lazyants-transkribus/transkribus-model-add-collection-by-id.md
What transkribus_model_add_collection_by_id does on Transkribus
AI agents use transkribus_model_add_collection_by_id 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_model_add_collection_by_id is rated Medium
The tool creates or modifies a relationship between a model and collection. While the blast radius is limited (affects only model-collection associations, not data deletion or external systems), misconfiguration or unauthorized additions could impair model functionality or expose collections inappropriately.
From the tool's definition Tool performs 'Add a collection to a model' — a state-changing operation that modifies model configuration by associating a collection with it. This is a reversible modification (collections can be removed), not destructive deletion.
Attacks that exploit this kind of access
The rule that runs transkribus_model_add_collection_by_id 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_model_add_collection_by_id, this is the rule to start with:
transkribus_model_add_collection_by_id 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_model_add_collection_by_id call is checked against it from then on.
Questions about transkribus_model_add_collection_by_id
Add a collection to a model by model ID and collection ID. 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_model_add_collection_by_id: 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_model_add_collection_by_id 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_model_add_collection_by_id 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_model_add_collection_by_id. 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_model_add_collection_by_id 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