transkribus_user_find

Search for users by username/email.

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-user-find.md

WHAT IT DOES

What transkribus_user_find does on Transkribus

AI agents call transkribus_user_find 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_user_find is rated Low

This tool retrieves user information without creating, modifying, deleting, executing code, or committing financial actions. It is a straightforward read/search operation limited to user lookup functionality.

From the tool's definition Tool name contains 'find' and description states 'Search for users by username/email' — a query operation with no modification or side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

transkribus_user_find Allowed

transkribus_user_find 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_user_find": {}
  }
}

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

FAQ

Questions about transkribus_user_find

What does the transkribus_user_find tool do? +

Search for users by username/email. 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_user_find? +

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

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

Can I rate-limit transkribus_user_find? +

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

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

transkribus_user_find 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

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