transkribus_search_tags

Search for tags, optionally filtered by collection or tag name.

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-search-tags.md

WHAT IT DOES

What transkribus_search_tags does on Transkribus

AI agents call transkribus_search_tags 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_search_tags is rated Low

This tool performs a search operation to retrieve or list tags based on optional filters. It does not create, modify, delete, or execute any operations—it only retrieves existing data. This is a classic Read category tool with low severity as it poses minimal risk if misused by an AI agent.

From the tool's definition Tool name 'transkribus_search_tags' and description 'Search for tags, optionally filtered by collection or tag name' indicates a query/retrieval operation with no side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

transkribus_search_tags Allowed

transkribus_search_tags 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_search_tags": {}
  }
}

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

FAQ

Questions about transkribus_search_tags

What does the transkribus_search_tags tool do? +

Search for tags, optionally filtered by collection or tag name. 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_search_tags? +

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

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

Can I rate-limit transkribus_search_tags? +

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

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

transkribus_search_tags 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_tags on Cocktails RAG MCP Server →search_torrents on M-Team MCP Server →aiva_search_customers on AIVA MCP Server →search_channel on YouTube MCP Server → The MCP Attack Database →

Guides

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