transkribus_coll_remove_user

Remove a user from a collection using the POST endpoint.

SERVERTranskribus SOURCE@lazyants/transkribus-mcp-server

Critical RISK CLASS

Category Destructive

Parameters 00 required

Recommended Hiddensee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-lazyants-transkribus/transkribus-coll-remove-user.md

WHAT IT DOES

What transkribus_coll_remove_user does on Transkribus

AI agents call transkribus_coll_remove_user to permanently remove resources in Transkribus, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

RISK

Why transkribus_coll_remove_user is rated Critical

Removing a user from a collection revokes their access rights, which is an irreversible action (the access is lost and must be explicitly re-granted). This is more than a write operation as it cannot be passively undone — it requires deliberate re-authorization. Misuse by an AI agent could lock legitimate users out of collections, causing significant disruption.

From the tool's definition Remove a user from a collection

Attacks that exploit this kind of access

RECOMMENDED RULE

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

transkribus_coll_remove_user Hidden

transkribus_coll_remove_user is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "transkribus_coll_remove_user"
  ]
}

RESTRICT THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about transkribus_coll_remove_user

What does the transkribus_coll_remove_user tool do? +

Remove a user from a collection using the POST endpoint. It is categorised as a Destructive tool in the Transkribus MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on transkribus_coll_remove_user? +

Register the Transkribus MCP server in PolicyLayer and add a rule for transkribus_coll_remove_user: 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_coll_remove_user? +

transkribus_coll_remove_user is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit transkribus_coll_remove_user? +

Yes. Add a rate_limit block to the transkribus_coll_remove_user 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_coll_remove_user completely? +

Set action: deny in the PolicyLayer policy for transkribus_coll_remove_user. 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_coll_remove_user? +

transkribus_coll_remove_user 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 → Critical-risk tools on this server →

Across the catalogue

remove_video on Mcptube Vision →delete_mysql_user on cPanel MCP Server →remove_concept on MegaMemory →task_assignees_remove on Vikunja → All critical-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Blast radius →Tool call approval →