transkribus_job_get_credit_transactions
Get credit transactions associated with a specific job.
This record as markdown: /tools/io-github-lazyants-transkribus/transkribus-job-get-credit-transactions.md
What transkribus_job_get_credit_transactions does on Transkribus
AI agents call transkribus_job_get_credit_transactions 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_job_get_credit_transactions is rated Low
This tool retrieves credit transaction data for audit or reporting purposes. It performs no modifications, deletions, or financial operations — it only reads existing transaction records. While the domain is financial (credit transactions), the tool itself does not move money, authorize charges, or create obligations; it merely retrieves historical data. Therefore, it is classified as Read rather than Financial.
From the tool's definition Tool name and description: 'Get credit transactions associated with a specific job' — the verb 'Get' and the read-only nature of retrieving transaction history indicate a query operation with no side effects.
Attacks that exploit this kind of access
The rule that runs transkribus_job_get_credit_transactions 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_job_get_credit_transactions, this is the rule to start with:
transkribus_job_get_credit_transactions 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_job_get_credit_transactions call is checked against it from then on.
Questions about transkribus_job_get_credit_transactions
Get credit transactions associated with a specific job. 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_job_get_credit_transactions: 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_job_get_credit_transactions 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_job_get_credit_transactions 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_job_get_credit_transactions. 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_job_get_credit_transactions 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