transkribus_doc_update_metadata_v2

Update document metadata using the v2 endpoint.

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-doc-update-metadata-v2.md

WHAT IT DOES

What transkribus_doc_update_metadata_v2 does on Transkribus

AI agents use transkribus_doc_update_metadata_v2 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_doc_update_metadata_v2 is rated Medium

This tool creates or modifies document metadata reversibly. It does not delete data (ruling out Destructive), execute arbitrary code (ruling out Execute), or involve financial transactions. The 'update' operation on metadata is a standard write action.

From the tool's definition Tool name contains 'update' and description states 'Update document metadata' — a write operation that modifies existing data.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

transkribus_doc_update_metadata_v2 Rate-limited

transkribus_doc_update_metadata_v2 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_doc_update_metadata_v2": {
      "limits": [
        {
          "counter": "transkribus_doc_update_metadata_v2_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_doc_update_metadata_v2 call is checked against it from then on.

FAQ

Questions about transkribus_doc_update_metadata_v2

What does the transkribus_doc_update_metadata_v2 tool do? +

Update document metadata using the v2 endpoint. 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_doc_update_metadata_v2? +

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

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

Can I rate-limit transkribus_doc_update_metadata_v2? +

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

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

transkribus_doc_update_metadata_v2 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

aroflo_create_or_update_record on AroFlo MCP →team_manager_update_budget on Team Manager MCP → The MCP Attack Database →

Guides

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