transkribus_auth_check_session
Check if the current Transkribus session is valid.
This record as markdown: /tools/io-github-lazyants-transkribus/transkribus-auth-check-session.md
What transkribus_auth_check_session does on Transkribus
AI agents call transkribus_auth_check_session 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_auth_check_session is rated Low
The tool performs a read-only validation check of an existing session. It has no side effects, does not modify data, does not execute code or commands, and does not delete or move resources. It is purely informational and falls clearly under the Read category with low severity since session validation poses minimal risk.
From the tool's definition Tool name and description: 'Check if the current Transkribus session is valid' — this is a query/status check operation that retrieves session state without modifying any data or triggering external actions.
Attacks that exploit this kind of access
The rule that runs transkribus_auth_check_session 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_auth_check_session, this is the rule to start with:
transkribus_auth_check_session 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_auth_check_session call is checked against it from then on.
Questions about transkribus_auth_check_session
Check if the current Transkribus session is valid. 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_auth_check_session: 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_auth_check_session 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_auth_check_session 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_auth_check_session. 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_auth_check_session 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