transkribus_doc_get_stats

Get detailed statistics for a document.

SERVERTranskribus SOURCE@lazyants/transkribus-mcp-server

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-lazyants-transkribus/transkribus-doc-get-stats.md

WHAT IT DOES

What transkribus_doc_get_stats does on Transkribus

AI agents call transkribus_doc_get_stats to retrieve information from Transkribus without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why transkribus_doc_get_stats is rated Low

This is a read-only operation that queries and returns statistical information about a document. There is no data creation, modification, deletion, code execution, or financial transaction. The tool merely retrieves existing information, making it a Read category risk with low severity.

From the tool's definition Tool name includes 'get' and description states 'Get detailed statistics for a document' — retrieves document statistics with no modification or side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

transkribus_doc_get_stats Allowed

transkribus_doc_get_stats is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "transkribus_doc_get_stats": {}
  }
}

ALLOW ONLY 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_get_stats call is checked against it from then on.

FAQ

Questions about transkribus_doc_get_stats

What does the transkribus_doc_get_stats tool do? +

Get detailed statistics for a document. It is categorised as a Read tool in the Transkribus MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on transkribus_doc_get_stats? +

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

transkribus_doc_get_stats is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit transkribus_doc_get_stats? +

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

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

transkribus_doc_get_stats 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

get_cocktail_by_category on Cocktails RAG MCP Server →get_torrent_detail on M-Team MCP Server →aiva_get_affiliate on AIVA MCP Server →get-chuck-categories on Jokes MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →