transkribus_user_activity_recognition
Get recognition activity history for a specific user.
This record as markdown: /tools/io-github-lazyants-transkribus/transkribus-user-activity-recognition.md
What transkribus_user_activity_recognition does on Transkribus
AI agents call transkribus_user_activity_recognition 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.
Why transkribus_user_activity_recognition is rated Low
This tool retrieves historical information about a user's recognition activity. It performs a read-only query against the Transkribus system with no capability to modify, delete, or execute operations. The blast radius of misuse is minimal—an attacker could view activity logs but cannot alter data or trigger actions. Low severity is appropriate for activity history retrieval.
From the tool's definition Tool name 'transkribus_user_activity_recognition' and description 'Get recognition activity history for a specific user' indicate a query/retrieval operation. The verb 'Get' and context of 'activity history' show data retrieval with no side effects.
Attacks that exploit this kind of access
The rule that runs transkribus_user_activity_recognition 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_activity_recognition, this is the rule to start with:
transkribus_user_activity_recognition is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Transkribus, apply this rule, and every transkribus_user_activity_recognition call is checked against it from then on.
Questions about transkribus_user_activity_recognition
Get recognition activity history for a specific user. It is categorised as a Read tool in the Transkribus MCP Server, which means it retrieves data without modifying state.
Register the Transkribus MCP server in PolicyLayer and add a rule for transkribus_user_activity_recognition: 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.
transkribus_user_activity_recognition is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the transkribus_user_activity_recognition 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.
Set action: deny in the PolicyLayer policy for transkribus_user_activity_recognition. 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.
transkribus_user_activity_recognition 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.
More on Transkribus, and thousands of servers like it.
This server
Across the catalogue