transkribus_server_get_events
Retrieve server events and notifications.
This record as markdown: /tools/io-github-lazyants-transkribus/transkribus-server-get-events.md
What transkribus_server_get_events does on Transkribus
AI agents call transkribus_server_get_events 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_server_get_events is rated Low
This tool retrieves/queries event and notification data from the server without creating, modifying, deleting, or executing any operations. The 'get' verb and 'retrieve' language in the description confirm a passive read operation. No side effects, destructive actions, or external code execution occur. Blast radius is minimal as misuse would only expose event logs that may already be accessible.
From the tool's definition Tool name contains 'get' and description states 'Retrieve server events and notifications' — both indicate a read-only query operation with no modification of data.
Attacks that exploit this kind of access
The rule that runs transkribus_server_get_events 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_server_get_events, this is the rule to start with:
transkribus_server_get_events 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_server_get_events call is checked against it from then on.
Questions about transkribus_server_get_events
Retrieve server events and notifications. 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_server_get_events: 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_server_get_events 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_server_get_events 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_server_get_events. 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_server_get_events 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