transkribus_crowdsource_unsubscribe

Unsubscribe from a crowdsourcing project for a collection.

SERVERTranskribus SOURCE@lazyants/transkribus-mcp-server

Medium RISK CLASS

Category Write

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-lazyants-transkribus/transkribus-crowdsource-unsubscribe.md

WHAT IT DOES

What transkribus_crowdsource_unsubscribe does on Transkribus

AI agents use transkribus_crowdsource_unsubscribe 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.

RISK

Why transkribus_crowdsource_unsubscribe is rated Medium

Unsubscribing from a crowdsourcing project modifies the user's or collection's membership/participation state. This is a reversible write operation (one could re-subscribe), not irreversible deletion. The blast radius is medium as it affects crowdsourcing participation for a collection but does not destroy data.

From the tool's definition Unsubscribe from a crowdsourcing project for a collection

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs transkribus_crowdsource_unsubscribe 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_crowdsource_unsubscribe, this is the rule to start with:

transkribus_crowdsource_unsubscribe Rate-limited

transkribus_crowdsource_unsubscribe 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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "transkribus_crowdsource_unsubscribe": {
      "limits": [
        {
          "counter": "transkribus_crowdsource_unsubscribe_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Transkribus, apply this rule, and every transkribus_crowdsource_unsubscribe call is checked against it from then on.

FAQ

Questions about transkribus_crowdsource_unsubscribe

What does the transkribus_crowdsource_unsubscribe tool do? +

Unsubscribe from a crowdsourcing project 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.

How do I enforce a policy on transkribus_crowdsource_unsubscribe? +

Register the Transkribus MCP server in PolicyLayer and add a rule for transkribus_crowdsource_unsubscribe: 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.

What risk level is transkribus_crowdsource_unsubscribe? +

transkribus_crowdsource_unsubscribe is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit transkribus_crowdsource_unsubscribe? +

Yes. Add a rate_limit block to the transkribus_crowdsource_unsubscribe 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.

How do I block transkribus_crowdsource_unsubscribe completely? +

Set action: deny in the PolicyLayer policy for transkribus_crowdsource_unsubscribe. 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.

What MCP server provides transkribus_crowdsource_unsubscribe? +

transkribus_crowdsource_unsubscribe 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.

KEEP EXPLORING

More on Transkribus, and thousands of servers like it.

This server

All 301 Transkribus tools →

Across the catalogue

The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →