get_document_snapshot
Get one point-in-time Huly document history snapshot and return markdown content. Resolve the document by teamspace plus document title or ID; resolve the snapshot by snapshotId, exact snapshot title, or exact createdOn timestamp. Prefer snapshotId from list_document_snapshots when titles or date...
This record as markdown: /tools/io-github-dearlordylord-huly-mcp/get-document-snapshot.md
What get_document_snapshot does on Huly
AI agents call get_document_snapshot to retrieve information from Huly without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why get_document_snapshot is rated Low
This tool retrieves a historical snapshot of a document and returns its content as markdown. There are no side effects, data modifications, or irreversible operations. It is a pure read operation that queries document history. The blast radius of misuse is minimal—an attacker gains visibility into historical document versions but cannot alter, delete, or execute operations through this tool.
From the tool's definition Tool description states 'Get one point-in-time Huly document history snapshot and return markdown content.' The verb 'Get' and the phrase 'return markdown content' indicate read-only retrieval.
Attacks that exploit this kind of access
The rule that runs get_document_snapshot safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Huly, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_document_snapshot, this is the rule to start with:
get_document_snapshot 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 Huly, apply this rule, and every get_document_snapshot call is checked against it from then on.
Questions about get_document_snapshot
Get one point-in-time Huly document history snapshot and return markdown content. Resolve the document by teamspace plus document title or ID; resolve the snapshot by snapshotId, exact snapshot title, or exact createdOn timestamp. Prefer snapshotId from list_document_snapshots when titles or dates may collide. Restore is out of scope. It is categorised as a Read tool in the Huly MCP Server, which means it retrieves data without modifying state.
Register the Huly MCP server in PolicyLayer and add a rule for get_document_snapshot: 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 Huly. Nothing to install.
get_document_snapshot 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 get_document_snapshot 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 get_document_snapshot. 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.
get_document_snapshot is provided by the Huly MCP server (@firfi/huly-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Huly, and thousands of servers like it.
This server
Across the catalogue