transkribus_server_bug_report
Submit a bug report to the Transkribus server.
This record as markdown: /tools/io-github-lazyants-transkribus/transkribus-server-bug-report.md
What transkribus_server_bug_report does on Transkribus
AI agents use transkribus_server_bug_report to create or update resources in Transkribus, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Transkribus environment.
Why transkribus_server_bug_report is rated Medium
Submitting a bug report creates a new record on the server. This is a write operation (creating data) with minimal blast radius — it cannot delete data, execute code, or cause financial harm. Misuse might result in spam reports but no serious consequences.
From the tool's definition Submit a bug report to the Transkribus server
Attacks that exploit this kind of access
The rule that runs transkribus_server_bug_report 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_bug_report, this is the rule to start with:
transkribus_server_bug_report stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. 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_bug_report call is checked against it from then on.
Questions about transkribus_server_bug_report
Submit a bug report to the Transkribus server. It is categorised as a Write tool in the Transkribus MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Transkribus MCP server in PolicyLayer and add a rule for transkribus_server_bug_report: 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_bug_report is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the transkribus_server_bug_report 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_bug_report. 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_bug_report 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