transkribus_page_update_hide_on_sites

Set whether a page is hidden on public sites.

SERVERTranskribus SOURCE@lazyants/transkribus-mcp-server
Medium RISK CLASS
Category Write
Parameters 00 required
Recommended Rate-limitedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-lazyants-transkribus/transkribus-page-update-hide-on-sites.md

What transkribus_page_update_hide_on_sites does on Transkribus

AI agents use transkribus_page_update_hide_on_sites 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_page_update_hide_on_sites is rated Medium

This tool modifies metadata (visibility/publication state) of a document page without deleting data or executing arbitrary operations. The change is reversible — pages can be unhidden. It affects content visibility on public sites, which could have reputational or access-control implications, warranting medium severity.

From the tool's definition Tool name contains 'update' and description states 'Set whether a page is hidden on public sites' — this modifies the visibility state of a page resource, a reversible configuration change.

Questions about transkribus_page_update_hide_on_sites

What does the transkribus_page_update_hide_on_sites tool do? +

Set whether a page is hidden on public sites. 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.

How do I enforce a policy on transkribus_page_update_hide_on_sites? +

Register the Transkribus MCP server in PolicyLayer and add a rule for transkribus_page_update_hide_on_sites: 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.

What risk level is transkribus_page_update_hide_on_sites? +

transkribus_page_update_hide_on_sites is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit transkribus_page_update_hide_on_sites? +

Yes. Add a rate_limit block to the transkribus_page_update_hide_on_sites 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.

How do I block transkribus_page_update_hide_on_sites completely? +

Set action: deny in the PolicyLayer policy for transkribus_page_update_hide_on_sites. 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.

What MCP server provides transkribus_page_update_hide_on_sites? +

transkribus_page_update_hide_on_sites 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.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Transkribus's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.