transkribus_crowd_post_project
Create or update the crowd project configuration for a collection.
This record as markdown: /tools/io-github-lazyants-transkribus/transkribus-crowd-post-project.md
What transkribus_crowd_post_project does on Transkribus
AI agents use transkribus_crowd_post_project 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_crowd_post_project is rated Medium
This tool modifies project configuration settings within a collection but does not delete data irreversibly or execute arbitrary code. Configuration changes can typically be undone or reverted. The blast radius is moderate—misuse could alter project settings affecting crowdsourcing workflows, but the impact is confined to configuration state rather than data destruction or financial consequences.
From the tool's definition Tool description explicitly states 'Create or update the crowd project configuration', which are reversible write operations on configuration data.
Attacks that exploit this kind of access
The rule that runs transkribus_crowd_post_project 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_crowd_post_project, this is the rule to start with:
transkribus_crowd_post_project 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_crowd_post_project call is checked against it from then on.
Questions about transkribus_crowd_post_project
Create or update the crowd project configuration for a collection. 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_crowd_post_project: 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_crowd_post_project 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_crowd_post_project 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_crowd_post_project. 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_crowd_post_project 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