transkribus_user_is_allowed_for_job
Check if the current user is allowed to run a specific job type.
This record as markdown: /tools/io-github-lazyants-transkribus/transkribus-user-is-allowed-for-job.md
What transkribus_user_is_allowed_for_job does on Transkribus
AI agents call transkribus_user_is_allowed_for_job 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_is_allowed_for_job is rated Low
This tool performs a read-only permission check. It queries whether a user has access to a job type but does not execute the job, modify permissions, create data, or delete anything. The operation is informational and has no side effects beyond returning a boolean or access status.
From the tool's definition Tool name contains 'is_allowed' and description states 'Check if the current user is allowed' — this is a query operation that retrieves authorization status without modifying any data or triggering side effects.
Attacks that exploit this kind of access
The rule that runs transkribus_user_is_allowed_for_job 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_is_allowed_for_job, this is the rule to start with:
transkribus_user_is_allowed_for_job 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_is_allowed_for_job call is checked against it from then on.
Questions about transkribus_user_is_allowed_for_job
Check if the current user is allowed to run a specific job type. 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_is_allowed_for_job: 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_is_allowed_for_job 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_is_allowed_for_job 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_is_allowed_for_job. 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_is_allowed_for_job 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