get_document
Get a document with all its pages. Returns sections[] where each has { id, name, html, order }. Use section.id as pageId for set_page_html/get_page_html/replace_html. To minimize tokens, pass includeHtml:false — sections come back as { id, name, order, type, label, htmlLength, htmlHash } only (no...
This record as markdown: /tools/cloud-easybits-easybits/get-document.md
What get_document does on EasyBits
AI agents call get_document to retrieve information from EasyBits 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 is rated Low
Retrieves document structure and content without modification or side effects.
From the tool's definition Get a document with all its pages. Returns sections with metadata.
Attacks that exploit this kind of access
The rule that runs get_document safely
PolicyLayer is an MCP gateway: it sits between your AI agents and EasyBits, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_document, this is the rule to start with:
get_document 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 EasyBits, apply this rule, and every get_document call is checked against it from then on.
Questions about get_document
Get a document with all its pages. Returns sections[] where each has { id, name, html, order }. Use section.id as pageId for set_page_html/get_page_html/replace_html. To minimize tokens, pass includeHtml:false — sections come back as { id, name, order, type, label, htmlLength, htmlHash } only (no html bodies). The htmlHash lets you detect server-side changes between reads without re-downloading. For full HTML of a single page, prefer get_page_html. See get_docs(\. It is categorised as a Read tool in the EasyBits MCP Server, which means it retrieves data without modifying state.
Register the EasyBits MCP server in PolicyLayer and add a rule for get_document: 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 EasyBits. Nothing to install.
get_document 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 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. 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 is provided by the EasyBits MCP server (@easybits.cloud/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on EasyBits, and thousands of servers like it.
This server
Across the catalogue